CVE-2026-35188 json
Double-free When Checking OCSP Stapled Response
published 2026-06-09 5 mo ago modified 2026-07-23 3 mo ago also EUVD-2026-35480
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
Issue summary: A malicious server can exploit TLS OCSP stapling by delivering a crafted response through the status_request extension, triggering a double-free in the client's certificate verification path.
Impact summary: Successful exploitation allows an attacker to corrupt heap memory via a double-free, potentially leading to a Denial of Service or possibly an attacker controlled code execution or other undefined behavior.
If OCSP stapling is enabled and the TLS client connects to a malicious server, a crafted OCSP stapled response can trigger a double free in the TLS client when the stapled response is checked.
The OCSP stapling is not enabled by default. Reliable code execution through a double-free is technically complex and highly environment-dependent but the Denial of Service impact is straightforward to achieve, warranting Moderate severity.
No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.
Patch / fix
- OpenSSL OpenSSL 3.6.3, 4.0.1
- openssl Debian 14 3.6.3-1
debian advisories DEBIAN-CVE-2026-35188
- bootupd hummingbird 1 0.3.2-1.hum1
- rust-bootupd hummingbird 1 0.3.2-1.hum1
- ruby3.4 hummingbird 1 3.4.10-31.7.hum1
- ruby3.4-libs hummingbird 1 3.4.10-31.7.hum1
- ruby3.4-bundled-gems hummingbird 1 3.4.10-31.7.hum1
- ruby3.4-default-gems hummingbird 1 3.4.10-31.7.hum1
- ruby4.0 hummingbird 1 4.0.6-37.3.hum1
- ruby4.0-libs hummingbird 1 4.0.6-37.3.hum1
red hat advisories RHSA-2026:67551RHSA-2026:62790RHSA-2026:62563RHSA-2026:62562RHSA-2026:55543RHSA-2026:42825
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-35188 updated cvss 5.9
openssl: Double-free When Checking OCSP Stapled Response
-
Red Hat Hardened Images bootupd 0.3.2-1.hum1, chunkah 0.6.0-3.hum1, openssl 3.5.8-0.1.hum1, openssl3 3.5.8-0.1.hum1, ruby4.0 4.0.6-37.3.hum1, ruby3.3 3.3.10-23.6.hum1, +20 morefixed: vendor fix RHSA-2026:67551
-
Red Hat Enterprise Linux 6 openssl, openssl-perl Red Hat Enterprise Linux 7 ovmf, OVMF, AAVMF Red Hat Enterprise Linux 8 edk2, shim, openssl, shim-x64, edk2-ovmf, shim-aa64, +9 more Red Hat Enterprise Linux 9 edk2, shim, openssl, shim-x64, edk2-ovmf, shim-aa64, +7 more Red Hat Enterprise Linux 10 edk2, shim, openssl, shim-unsigned-x64, shim-unsigned-aarch64 Red Hat Hardened Images rust, unbound, netavark, openshell, rust-podman-sequoia, rubygem3.3-rbs 3.4.0-23.6.hum1, +50 morenot affected: vulnerable code not present
+4 more productsfewer
Red Hat JBoss Core Services jbcs-httpd24-openssl, jbcs-httpd24-openssl-libs, jbcs-httpd24-openssl-perl, jbcs-openssl-win6-x86_64.zip 3.5.5-SP4 Red Hat JBoss Web Server 6 jws-optional-native-components-win6-x86_64.zip 6.2.4.ER1 Red Hat JBoss Web Server 7 jws-optional-native-components-win6-x86_64.zip 6.2.4.ER1 Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 4 mo ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L |
Affected products
- OpenSSL OpenSSL
Classification
- Weakness
-
- CWE-415 Double Free
- Technology feeds
References
Sources
- CVE List CVE-2026-35188
- NVD CVE-2026-35188
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.