CVE-2026-34580: CWE-295: Improper Certificate Validation in randombit botan
CVE-2026-34580 is a critical vulnerability in the Botan C++ cryptography library versions 3. 11. 0 to before 3. 11. 1. The function Certificate_Store::certificate_known incorrectly returns true if any certificate in the store has a matching distinguished name (DN) and subject key identifier, without verifying that the certificates are identical. This flaw causes the path validation logic to mistakenly accept an end entity certificate as a trusted root if it shares these attributes, potentially allowing unauthorized certificates to be trusted. The issue is fixed in version 3. 11. 1.
AI Analysis
Technical Summary
Botan 3.11.0 contains a certificate validation vulnerability (CWE-295) where Certificate_Store::certificate_known returns true based on matching DN and subject key identifier without confirming certificate identity. This leads to improper acceptance of end entity certificates as trusted roots during path validation. The vulnerability is addressed in Botan 3.11.1.
Potential Impact
An attacker could present an end entity certificate with a DN and subject key identifier matching a trusted root, causing the library to accept it as a trusted root certificate. This undermines the trust model of certificate validation, potentially allowing unauthorized certificates to be accepted as trusted, which can lead to man-in-the-middle attacks or other cryptographic trust violations.
Mitigation Recommendations
This vulnerability is fixed in Botan version 3.11.1. Users should upgrade to version 3.11.1 or later to remediate the issue. No other official remediation or temporary fixes are documented. Patch status is confirmed by the vendor's versioning information.
CVE-2026-34580: CWE-295: Improper Certificate Validation in randombit botan
Description
CVE-2026-34580 is a critical vulnerability in the Botan C++ cryptography library versions 3. 11. 0 to before 3. 11. 1. The function Certificate_Store::certificate_known incorrectly returns true if any certificate in the store has a matching distinguished name (DN) and subject key identifier, without verifying that the certificates are identical. This flaw causes the path validation logic to mistakenly accept an end entity certificate as a trusted root if it shares these attributes, potentially allowing unauthorized certificates to be trusted. The issue is fixed in version 3. 11. 1.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Botan 3.11.0 contains a certificate validation vulnerability (CWE-295) where Certificate_Store::certificate_known returns true based on matching DN and subject key identifier without confirming certificate identity. This leads to improper acceptance of end entity certificates as trusted roots during path validation. The vulnerability is addressed in Botan 3.11.1.
Potential Impact
An attacker could present an end entity certificate with a DN and subject key identifier matching a trusted root, causing the library to accept it as a trusted root certificate. This undermines the trust model of certificate validation, potentially allowing unauthorized certificates to be accepted as trusted, which can lead to man-in-the-middle attacks or other cryptographic trust violations.
Mitigation Recommendations
This vulnerability is fixed in Botan version 3.11.1. Users should upgrade to version 3.11.1 or later to remediate the issue. No other official remediation or temporary fixes are documented. Patch status is confirmed by the vendor's versioning information.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-30T16:56:30.999Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d5779eaaed68159a6ad780
Added to database: 4/7/2026, 9:31:10 PM
Last enriched: 4/15/2026, 12:34:56 PM
Last updated: 5/22/2026, 2:53:24 PM
Views: 90
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.