{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-35188 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-35188 is a medium-severity use after free vulnerability in Openssl Openssl, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35188 and fix it if it is affected.\n\nWhat it is: CVE-2026-35188 is a medium-severity use after free vulnerability in Openssl Openssl, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-35188 in the wild and no public exploit code.\n\nAffected product: Openssl Openssl. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-35188/ (Markdown: https://insights.sbomify.com/CVE-2026-35188/index.md)","id":"CVE-2026-35188","markdown":"https://insights.sbomify.com/CVE-2026-35188/index.md","name":"CVE-2026-35188","record":{"aliases":["DEBIAN-CVE-2026-35188","GHSA-vc8w-w49c-4jgj","UBUNTU-CVE-2026-35188"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenSSL TLS library","requires_auth":"low_privilege","summary":"A malicious server can trigger a double-free in OpenSSL clients via crafted OCSP stapled responses, causing denial of service or potential code execution.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"openssl","cpe":[{"product":"openssl","vendor":"openssl"}],"cvss":{"score":5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-415","name":"Double Free"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Double-free When Checking OCSP Stapled Response","id":"CVE-2026-35188","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"openssl:openssl","products":["openssl:openssl"],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Excessive Memory Allocation in Relative CRLDP Processing","id":"CVE-2026-35189"},"packages":[],"prev":{"headline":"pyLoad has SSRF in parse_urls API endpoint via unvalidated URL parameter","id":"CVE-2026-35187"},"products":["OpenSSL"],"published":"2026-06-09","related":[{"cvss_score":10,"headline":"Null dereference in n/a","id":"CVE-2009-3245","kev_date_added":null,"published":"2010-03-05"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2006-3738","kev_date_added":null,"published":"2006-09-28"},{"cvss_score":9.8,"headline":"Untrusted Sender DN Used as Format String in CMP Response Validation","id":"CVE-2026-63073","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2016-6309","kev_date_added":null,"published":"2016-09-26"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-0799","kev_date_added":null,"published":"2016-03-03"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-2842","kev_date_added":null,"published":"2016-03-03"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2003-0545","kev_date_added":null,"published":"2003-10-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-10","vendors":["OpenSSL"]},"summary":"A malicious server can trigger a double-free in OpenSSL clients via crafted OCSP stapled responses, causing denial of service or potential code execution.","url":"https://insights.sbomify.com/CVE-2026-35188/"}