CVE-2026-35188

{"id": "CVE-2026-35188", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-35188", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-06-10T03:59:37.106557Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.0, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "LOW", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 3.4, "exploitabilityScore": 1.6}]}, "affected": [{"source": "openssl-security@openssl.org", "affectedData": [{"vendor": "OpenSSL", "product": "OpenSSL", "versions": [{"status": "affected", "version": "4.0.0", "lessThan": "4.0.1", "versionType": "semver"}, {"status": "affected", "version": "3.6.0", "lessThan": "3.6.3", "versionType": "semver"}], "defaultStatus": "unaffected"}]}], "published": "2026-06-09T17:17:05.437", "references": [{"url": "https://github.com/openssl/openssl/commit/131145d25659e8749a9ed1afb383484854cffb78", "tags": ["Patch"], "source": "openssl-security@openssl.org"}, {"url": "https://github.com/openssl/openssl/commit/78d0154cffda03aaaac63a087cc523a6b35fa8fd", "tags": ["Patch"], "source": "openssl-security@openssl.org"}, {"url": "https://openssl-library.org/news/secadv/20260609.txt", "tags": ["Vendor Advisory"], "source": "openssl-security@openssl.org"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "openssl-security@openssl.org", "description": [{"lang": "en", "value": "CWE-415"}]}], "descriptions": [{"lang": "en", "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."}, {"lang": "es", "value": "Resumen del problema: Un servidor malicioso puede explotar el 'TLS OCSP stapling' entregando una respuesta manipulada a trav\u00e9s de la 'extension status_request', desencadenando un 'double-free' en la ruta de verificaci\u00f3n de certificados del cliente.\n\nResumen del impacto: La explotaci\u00f3n exitosa permite a un atacante corromper la memoria 'heap' a trav\u00e9s de un 'double-free', lo que podr\u00eda llevar a una denegaci\u00f3n de servicio o posiblemente a una ejecuci\u00f3n de c\u00f3digo controlada por el atacante u otro comportamiento indefinido.\n\nSi el 'OCSP stapling' est\u00e1 habilitado y el cliente TLS se conecta a un servidor malicioso, una respuesta 'OCSP stapled' manipulada puede desencadenar un 'double free' en el cliente TLS cuando se verifica la respuesta 'stapled'.\n\nEl 'OCSP stapling' no est\u00e1 habilitado por defecto. La ejecuci\u00f3n de c\u00f3digo fiable a trav\u00e9s de un 'double-free' es t\u00e9cnicamente compleja y altamente dependiente del entorno, pero el impacto de denegaci\u00f3n de servicio es sencillo de lograr, lo que justifica una severidad Moderada.\n\nNing\u00fan m\u00f3dulo FIPS se ve afectado por este problema, ya que el c\u00f3digo afectado est\u00e1 fuera del l\u00edmite del m\u00f3dulo FIPS de OpenSSL."}], "lastModified": "2026-07-23T08:10:00.137", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "D41B3C45-EC73-4DC8-989D-B2E2792E102F", "versionEndExcluding": "3.6.3", "versionStartIncluding": "3.6.0"}, {"criteria": "cpe:2.3:a:openssl:openssl:4.0.0:-:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "6E881B9A-1A0A-4BC0-8160-20C00561167D"}], "operator": "OR"}]}], "sourceIdentifier": "openssl-security@openssl.org"}