{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34580 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-34580 is a critical authentication bypass vulnerability in randombit botan, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34580 and fix it if it is affected.\n\nWhat it is: CVE-2026-34580 is a critical authentication bypass vulnerability in randombit botan, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-34580 in the wild and no public exploit code.\n\nAffected product: randombit botan. 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-34580/ (Markdown: https://insights.sbomify.com/CVE-2026-34580/index.md)","id":"CVE-2026-34580","markdown":"https://insights.sbomify.com/CVE-2026-34580/index.md","name":"CVE-2026-34580","record":{"aliases":["ALPINE-CVE-2026-34580","GHSA-v782-6fq4-q827","UBUNTU-CVE-2026-34580"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"C++ cryptography library","requires_auth":"none","summary":"Attackers can bypass certificate authentication by presenting an end-entity certificate with a matching DN to a trusted root, leading to unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"botan","vendor":"botan_project"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Botan is a C++ cryptography library. In 3.11.0, the function Certificate_Store::certificate_known had a misleading name; it would return true if any certificate in the store had a DN (and subject key identifier, if set) matching that of the argument. It did not check that the cert it found and the cert it was passed were actually the same certificate. In 3.11.0 an extension of path validation logic was made which assumed that certificate_known only returned true if the certificates were in fact identical. The impact is that if an end entity certificate is presented, and its DN (and subject key identifier, if set) match that of any trusted root, the end entity certificate is accepted immediately as if it itself were a trusted root. , This vulnerability is fixed in 3.11.1.","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":"Botan has a certificate authentication bypass due to trust anchor confusion","id":"CVE-2026-34580","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"goshs has Auth Bypass via Share Token","id":"CVE-2026-34581"},"packages":[],"prev":{"headline":"MantisBT has an authorization bypass via private issue monitoring","id":"CVE-2026-34579"},"products":["botan"],"published":"2026-04-07","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2021-24115","kev_date_added":null,"published":"2021-02-22"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2018-9127","kev_date_added":null,"published":"2018-04-02"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2015-7826","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2016-6878","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-9132","kev_date_added":null,"published":"2017-01-30"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-2195","kev_date_added":null,"published":"2016-05-13"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-2196","kev_date_added":null,"published":"2016-05-13"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["randombit"]},"summary":"Attackers can bypass certificate authentication by presenting an end-entity certificate with a matching DN to a trusted root, leading to unauthorized access.","url":"https://insights.sbomify.com/CVE-2026-34580/"}