Double-free When Checking OCSP Stapled Response
Summary
| CVE | CVE-2026-35188 |
|---|---|
| State | PUBLISHED |
| Assigner | openssl |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-06-09 17:17:05 UTC |
| Updated | 2026-06-15 18:12:24 UTC |
| Description | 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. |
Risk And Classification
Primary CVSS: v3.1 5 MEDIUM from ADP
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS: 0.002260000 probability, percentile 0.131160000 (date 2026-06-21)
Problem Types: CWE-415 | CWE-415 CWE-415 Double Free
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | ADP | DECLARED | 5 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L |
| 3.1 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | Secondary | 5 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
HighPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
LowIntegrity
LowAvailability
LowCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
NVD Known Affected Configurations (CPE 2.3)
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/openssl/openssl/commit/78d0154cffda03aaaac63a087cc523a6b35fa8fd | [email protected] | github.com | Patch |
| github.com/openssl/openssl/commit/131145d25659e8749a9ed1afb383484854cffb78 | [email protected] | github.com | Patch |
| openssl-library.org/news/secadv/20260609.txt | [email protected] | openssl-library.org | Vendor Advisory |
| github.com/openssl/security/commit/131145d25659e8749a9ed1afb383484854cffb78 | MITRE | github.com | |
| github.com/openssl/security/commit/78d0154cffda03aaaac63a087cc523a6b35fa8fd | MITRE | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Wang Kenaz (University of Illinois) (en)
CNA: Guido Vranken (Aisle Research) (en)
CNA: Aaron Grattafiori (Nvidia) (en)
CNA: Daniel Kubec (en)
There are currently no legacy QID mappings associated with this CVE.