7.5

CVE-2026-54876: Client-Side Memory Leak in OCSP Response Checking

Awaiting analysis
AliasesRHSA-2026:57021UBUNTU-CVE-2026-54876DEBIAN-CVE-2026-54876
Published 05-08-2026Last modified 05-08-2026

Vulnerability summary

CVE-2026-54876 is a high (CVSS 7.5) vulnerability in openssl. EPSS estimates a 0.52% chance of exploitation in the next 30 days, higher than 44.5% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 7.5 (CVE.org); no exploitation reported by the 5 checked sources; EPSS 1% (FIRST, 03-11-2026)

Source freshness unavailable

How is this decided?
CVSS score
7.5/10
010
High · v3.1 (CVE.org)
EPSS score
0.52%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 6 · Related 1

Timeline

  1. 05-08-2026
    PublishedVulnerability first disclosed.
  2. 05-08-2026
    Last modifiedVulnerability information updated.

Description

Issue summary: A malicious TLS server can cause a memory leak in a TLS client that has enabled OCSP response checking by sending an OCSP response that contains no single response entries. Impact summary: An attacker can leak an attacker-tunable amount of memory per TLS handshake in a victim client application. A long-running client that repeatedly connects to a malicious server can have its memory exhausted, resulting in a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: The affected function is called during X.509 certificate chain verification when OCSP response checking is enabled with the X509_V_FLAG_OCSP_RESP_CHECK or X509_V_FLAG_OCSP_RESP_CHECK_ALL verification flags, for example when a TLS client verifies an OCSP response stapled into the TLS handshake by the server. When the received BasicOCSPResponse contains an empty SEQUENCE OF SingleResponse, which is permitted on the wire and accepted by the OpenSSL decoder, the OCSP_BASICRESP structure allocated by OCSP_response_get1_basic() was not freed because an early return bypassed the cleanup code at the end of the function. The amount of memory leaked per handshake can be amplified by the attacker by padding the certs field of the BasicOCSPResponse with bogus certificates, which are parsed and stored in the leaked structure before the empty response check triggers the early return. A long-running TLS client that repeatedly connects to a malicious server can have its memory exhausted over time. OCSP response checking is not enabled by default. Only client applications that explicitly enable the OCSP response check verification flags are affected. FIPS impact: no The FIPS modules in 4.0 and 3.6 are not affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.

CVSS metrics

7 scores · 7 sources · 1 version

EPSS trend

Probability

0.52%

Chance of exploitation in the next 30 days

Percentile

45%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.52% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Chainguard16 products
  • eco-python-openssl-4< 4.0.2-r0
  • eco-python-openssl-4-pyca< 4.0.2-r0
  • eco-python-openssl-4-pyca-dev< 4.0.2-r0
  • libcrypto3< 3.6.3-r4
  • libcrypto3-2.34< 3.6.3-r2
Wolfi10 products
  • libcrypto3< 3.6.3-r4
  • libssl3< 3.6.3-r4
  • openssl< 3.6.3-r4
  • openssl-4.0< 4.0.2-r0
  • openssl-4.0-libcrypto< 4.0.2-r0
Redhat4 products
  • openssl3< 0:3.5.7-2.2.hum1
  • openssl3-devel< 0:3.5.7-2.2.hum1
  • openssl3-devel-engine< 0:3.5.7-2.2.hum1
  • openssl3-libs< 0:3.5.7-2.2.hum1
Debian1 product
  • openssl< 3.6.4-1
Openssl1 product
  • openssl≥ 4.0.0, < 4.0.2 | ≥ 3.6.0, < 3.6.4
Ubuntu1 product
  • nodejsAll versions (No fix recorded)

6 vendors · 33 products

References

15 links
Show all 15 references