Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Impact | The CVSS 5.9 score with AV:N/AC:H reflects moderate severity with network accessibility but high complexity due to the need for specific network positioning. EPSS data is not provided, but the missing signature verification is a critical control bypass. The vulnerability is not confirmed as actively exploited (KEV status not provided), and no public exploit code has been identified in the available intelligence. However, the impact is significant: integrity is rated as HIGH (I:H), meaning an attacker can modify certificate status information. The high complexity requirement (AC:H) stems from the need to intercept or influence OCSP responses, limiting real-world exploitation but not eliminating it-particularly in enterprise or ISP-level attack scenarios. This is a genuine priority for applications relying on OCSP validation; it is not a low-real-risk high-CVSS case. Organizations using Botan for PKI operations should treat this as critical. |
| Exploit ScenarioDerived | An attacker positioned on the network path between a Botan application and an OCSP responder could intercept OCSP requests and respond with a forged response claiming a revoked certificate is 'good', bypassing revocation checks. No signature verification means the fraudulent response is accepted as legitimate. This could allow use of a compromised or revoked TLS certificate in encrypted sessions, potentially enabling man-in-the-middle attacks or impersonation. Attack complexity is high because the attacker must intercept network traffic or compromise the OCSP responder, but the scenario is realistic in corporate networks or ISP-level compromises. No public exploit code has been identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 30, 2026
Botan cryptography library versions 3.0.0 through 3.10.x fail to verify OCSP response signatures during X.509 certificate path validation, allowing attackers to forge certificate status responses and potentially bypass revocation checks. This integrity bypass affects any application using Botan for TLS or certificate validation and requires network positioning but not authentication. The vulnerability was patched in version 3.11.0.
RemediationAI
Upgrade Botan to version 3.11.0 or later immediately. This release includes the signature verification fix for OCSP responses. Users unable to upgrade should disable OCSP validation temporarily if feasible, though this weakens revocation checking and is not a long-term solution. Patch availability is confirmed; Botan 3.11.0 contains the upstream fix. Consult the GitHub security advisory at https://github.com/randombit/botan/security/advisories/GHSA-9j2j-hqmc-hf5x for detailed guidance and version-specific deployment notes.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Botan is a C++ cryptography library widely used for TLS, PKI, and cryptographic operations. During X.509 path validation, the library processes OCSP (Online Certificate Status Protocol) responses to determine whether certificates have been revoked. The vulnerability stems from a missing cryptographic signature verification step (CWE-347: Improper Verification of Cryptographic Signature). While Botan correctly checked that OCSP responses contained an appropriate status code (e.g., 'good', 'revoked', 'unknown'), it did not validate the OCSP response's digital signature, which authenticates the response's origin and integrity. An attacker positioned to intercept or manipulate OCSP responses could craft fraudulent responses with valid-looking status codes, making revoked certificates appear valid.
Know when Botan gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Primary rating from GitHub Advisory.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
Botan is a C++ cryptography library. From version 3.0.0 to before version 3.11.0, during X509 path validation, OCSP responses were checked for an appropriate status code, but critically omitted verifying the signature of the OCSP response itself. This issue has been patched in version 3.11.0.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Integer overflow in the PointGFp constructor in Botan before 1.10.11 and 1.11.x before 1.11.27 allows remote attackers t
Heap-based buffer overflow in the P-521 reduction function in Botan 1.11.x before 1.11.27 allows remote attackers to cau
A programming error exists in a way Randombit Botan cryptographic library version 2.0.1 implements x500 string compariso
Botan before 3.6.0, when certain GCC versions are used, has a compiler-induced secret-dependent operation in lib/utils/d
Botan before 3.6.0, when certain LLVM versions are used, has compiler-induced secret-dependent control flow in lib/utils
The ElGamal implementation in Botan through 2.18.1, as used in Thunderbird and other products, allows plaintext recovery
Botan 2.5.0 through 2.6.0 before 2.7.0 allows a memory-cache side-channel attack on ECDSA signatures, aka the Return Of
botan 1.11.x before 1.11.22 improperly handles wildcard matching against hostnames, which might allow remote attackers t
The Curve25519 code in botan before 1.11.31, on systems without a native 128-bit integer type, might allow attackers to
In Botan 1.8.0 through 1.11.33, when decoding BER data an integer overflow could occur, which would cause an incorrect l
In Botan before 2.17.3, constant-time computations are not used for certain decoding and encoding operations (base32, ba
Botan 2.2.0 - 2.4.0 (fixed in 2.5.0) improperly handled wildcard certificates and could accept certain certificates as v
EUVD-2026-17211
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB