{"api_version":"1","generated_at":"2026-06-10T13:42:41+00:00","cve":"CVE-2026-35188","urls":{"html":"https://cve.report/CVE-2026-35188","api":"https://cve.report/api/cve/CVE-2026-35188.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-35188","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-35188"},"summary":{"title":"Double-free When Checking OCSP Stapled Response","description":"Issue summary: A malicious server can exploit TLS OCSP stapling by delivering\na crafted response through the status_request extension, triggering a\ndouble-free in the client's certificate verification path.\n\nImpact summary: Successful exploitation allows an attacker to corrupt heap\nmemory via a double-free, potentially leading to a Denial of Service or\npossibly an attacker controlled code execution or other undefined behavior.\n\nIf OCSP stapling is enabled and the TLS client connects to a malicious server,\na crafted OCSP stapled response can trigger a double free in the TLS client\nwhen the stapled response is checked.\n\nThe OCSP stapling is not enabled by default. Reliable code execution\nthrough a double-free is technically complex and highly environment-dependent\nbut the Denial of Service impact is straightforward to achieve, warranting\nModerate severity.\n\nNo FIPS modules are affected by this issue as the affected code is outside\nthe OpenSSL FIPS module boundary.","state":"PUBLISHED","assigner":"openssl","published_at":"2026-06-09 17:17:05","updated_at":"2026-06-10 08:16:23"},"problem_types":["CWE-415","CWE-415 CWE-415 Double Free"],"metrics":[],"references":[{"url":"https://github.com/openssl/openssl/commit/78d0154cffda03aaaac63a087cc523a6b35fa8fd","name":"https://github.com/openssl/openssl/commit/78d0154cffda03aaaac63a087cc523a6b35fa8fd","refsource":"openssl-security@openssl.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/openssl/openssl/commit/131145d25659e8749a9ed1afb383484854cffb78","name":"https://github.com/openssl/openssl/commit/131145d25659e8749a9ed1afb383484854cffb78","refsource":"openssl-security@openssl.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://openssl-library.org/news/secadv/20260609.txt","name":"https://openssl-library.org/news/secadv/20260609.txt","refsource":"openssl-security@openssl.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/openssl/security/commit/131145d25659e8749a9ed1afb383484854cffb78","name":"https://github.com/openssl/security/commit/131145d25659e8749a9ed1afb383484854cffb78","refsource":"MITRE","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/openssl/security/commit/78d0154cffda03aaaac63a087cc523a6b35fa8fd","name":"https://github.com/openssl/security/commit/78d0154cffda03aaaac63a087cc523a6b35fa8fd","refsource":"MITRE","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-35188","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-35188","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"OpenSSL","product":"OpenSSL","version":"affected 4.0.0 4.0.1 semver","platforms":[]},{"source":"CNA","vendor":"OpenSSL","product":"OpenSSL","version":"affected 3.6.0 3.6.3 semver","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"Wang Kenaz (University of Illinois)","lang":"en"},{"source":"CNA","value":"Guido Vranken (Aisle Research)","lang":"en"},{"source":"CNA","value":"Aaron Grattafiori (Nvidia)","lang":"en"},{"source":"CNA","value":"Daniel Kubec","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-35188","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"role":"CISA Coordinator","timestamp":"2026-06-09T00:00:00+00:00","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-06-10T03:59:36.315Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"defaultStatus":"unaffected","product":"OpenSSL","vendor":"OpenSSL","versions":[{"lessThan":"4.0.1","status":"affected","version":"4.0.0","versionType":"semver"},{"lessThan":"3.6.3","status":"affected","version":"3.6.0","versionType":"semver"}]}],"credits":[{"lang":"en","type":"reporter","value":"Wang Kenaz (University of Illinois)"},{"lang":"en","type":"reporter","value":"Guido Vranken (Aisle Research)"},{"lang":"en","type":"reporter","value":"Aaron Grattafiori (Nvidia)"},{"lang":"en","type":"remediation developer","value":"Daniel Kubec"}],"datePublic":"2026-06-09T14:00:00.000Z","descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"Issue summary: A malicious server can exploit TLS OCSP stapling by delivering<br>a crafted response through the status_request extension, triggering a<br>double-free in the client's certificate verification path.<br><br>Impact summary: Successful exploitation allows an attacker to corrupt heap<br>memory via a double-free, potentially leading to a Denial of Service or<br>possibly an attacker controlled code execution or other undefined behavior.<br><br>If OCSP stapling is enabled and the TLS client connects to a malicious server,<br>a crafted OCSP stapled response can trigger a double free in the TLS client<br>when the stapled response is checked.<br><br>The OCSP stapling is not enabled by default. Reliable code execution<br>through a double-free is technically complex and highly environment-dependent<br>but the Denial of Service impact is straightforward to achieve, warranting<br>Moderate severity.<br><br>No FIPS modules are affected by this issue as the affected code is outside<br>the OpenSSL FIPS module boundary."}],"value":"Issue summary: A malicious server can exploit TLS OCSP stapling by delivering\na crafted response through the status_request extension, triggering a\ndouble-free in the client's certificate verification path.\n\nImpact summary: Successful exploitation allows an attacker to corrupt heap\nmemory via a double-free, potentially leading to a Denial of Service or\npossibly an attacker controlled code execution or other undefined behavior.\n\nIf OCSP stapling is enabled and the TLS client connects to a malicious server,\na crafted OCSP stapled response can trigger a double free in the TLS client\nwhen the stapled response is checked.\n\nThe OCSP stapling is not enabled by default. Reliable code execution\nthrough a double-free is technically complex and highly environment-dependent\nbut the Denial of Service impact is straightforward to achieve, warranting\nModerate severity.\n\nNo FIPS modules are affected by this issue as the affected code is outside\nthe OpenSSL FIPS module boundary."}],"metrics":[{"format":"other","other":{"content":{"text":"Moderate"},"type":"https://openssl-library.org/policies/general/security-policy/"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-415","description":"CWE-415 Double Free","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-06-10T07:47:57.674Z","orgId":"3a12439a-ef3a-4c79-92e6-6081a721f1e5","shortName":"openssl"},"references":[{"name":"OpenSSL Advisory","tags":["vendor-advisory"],"url":"https://openssl-library.org/news/secadv/20260609.txt"},{"name":"4.0.1 git commit","tags":["patch"],"url":"https://github.com/openssl/openssl/commit/78d0154cffda03aaaac63a087cc523a6b35fa8fd"},{"name":"3.6.3 git commit","tags":["patch"],"url":"https://github.com/openssl/openssl/commit/131145d25659e8749a9ed1afb383484854cffb78"}],"source":{"discovery":"UNKNOWN"},"title":"Double-free When Checking OCSP Stapled Response","x_generator":{"engine":"Vulnogram 0.2.0"}}},"cveMetadata":{"assignerOrgId":"3a12439a-ef3a-4c79-92e6-6081a721f1e5","assignerShortName":"openssl","cveId":"CVE-2026-35188","datePublished":"2026-06-09T16:03:24.395Z","dateReserved":"2026-04-01T17:36:26.323Z","dateUpdated":"2026-06-10T07:47:57.674Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-09 17:17:05","lastModifiedDate":"2026-06-10 08:16:23","problem_types":["CWE-415","CWE-415 CWE-415 Double Free"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"35188","Ordinal":"1","Title":"Double-free When Checking OCSP Stapled Response","CVE":"CVE-2026-35188","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"35188","Ordinal":"1","NoteData":"Issue summary: A malicious server can exploit TLS OCSP stapling by delivering\na crafted response through the status_request extension, triggering a\ndouble-free in the client's certificate verification path.\n\nImpact summary: Successful exploitation allows an attacker to corrupt heap\nmemory via a double-free, potentially leading to a Denial of Service or\npossibly an attacker controlled code execution or other undefined behavior.\n\nIf OCSP stapling is enabled and the TLS client connects to a malicious server,\na crafted OCSP stapled response can trigger a double free in the TLS client\nwhen the stapled response is checked.\n\nThe OCSP stapling is not enabled by default. Reliable code execution\nthrough a double-free is technically complex and highly environment-dependent\nbut the Denial of Service impact is straightforward to achieve, warranting\nModerate severity.\n\nNo FIPS modules are affected by this issue as the affected code is outside\nthe OpenSSL FIPS module boundary.","Type":"Description","Title":"Double-free When Checking OCSP Stapled Response"}]}}}