CVE-2026-32883: 
Botan vulnerability analysis and mitigation

CVE-2026-32883 is a missing OCSP response signature verification vulnerability in the Botan C++ cryptography library that allows a man-in-the-middle (MitM) attacker to bypass certificate revocation checks during X.509 path validation. Affecting Botan versions 3.0.0 through 3.10.x (the bug was introduced in 3.0.0 and does not affect the 2.x branch), the flaw was published on March 30, 2026, and patched in version 3.11.0. It carries a CVSS v3.1 base score of 5.9 (Medium) (GitHub Advisory).

The root cause is classified as CWE-347 (Improper Verification of Cryptographic Signature) and CWE-299 (Improper Check for Certificate Revocation). During X.509 path validation, Botan's OCSP handling code checked the status code field of an OCSP response to determine certificate revocation status, but entirely omitted verifying the cryptographic signature on the OCSP response itself. Because OCSP is typically served over plain HTTP, an attacker positioned between a Botan-based client and the OCSP responder can intercept and tamper with the response body — substituting a forged "good" status for a revoked certificate — without any detection by the library. Realistic network-level attack vectors include DNS hijacking, BGP hijacking, or a rogue wireless access point (GitHub Advisory).

Successful exploitation allows an attacker to present a revoked or otherwise fraudulent TLS certificate as valid to any application relying on Botan for X.509 path validation, effectively bypassing certificate revocation enforcement. This compromises the integrity of certificate validation and enables MitM attacks against encrypted communications, potentially exposing sensitive data in transit or facilitating impersonation of trusted services. There is no direct confidentiality or availability impact from the vulnerability itself, but the downstream consequences of accepting fraudulent certificates can be severe depending on the application context (GitHub Advisory, Feedly).

1. Reconnaissance: Identify applications or services using Botan versions 3.0.0–3.10.x for TLS/X.509 certificate validation, particularly those that perform OCSP-based revocation checking.
2. Establish MitM position: Position between the target Botan-based client and the OCSP responder using DNS hijacking, BGP route injection, or a rogue network access point to intercept OCSP HTTP traffic.
3. Intercept OCSP request: Capture the outbound OCSP request (plain HTTP) sent by the Botan client to the OCSP responder URL embedded in the target certificate.
4. Forge OCSP response: Craft a forged OCSP response containing a "good" status for a certificate that is actually revoked, without a valid signature (since Botan does not verify the signature).
5. Deliver forged response: Return the unsigned or improperly signed forged OCSP response to the Botan client in place of the legitimate responder's reply.
6. Bypass revocation check: Botan accepts the forged response as valid (checking only the status code), causing the revoked certificate to pass X.509 path validation and enabling the attacker to impersonate the certificate holder in subsequent communications (GitHub Advisory).

• Network: Unexpected DNS resolutions or HTTP responses for OCSP responder URLs originating from non-authoritative IP addresses; OCSP HTTP responses lacking a valid Content-Type: application/ocsp-response header or with anomalous response sizes.
• Network: OCSP traffic (typically TCP port 80) to OCSP responder hostnames being redirected to unfamiliar IP addresses, detectable via DNS query logs or network flow analysis.
• Logs: Application or TLS library logs showing successful certificate validation for certificates that should be revoked; absence of OCSP signature verification error messages in Botan debug output for versions 3.0.0–3.10.x.
• Network: BGP route anomalies or unexpected route changes affecting OCSP responder prefixes, observable via BGP monitoring tools.

The primary remediation is to upgrade Botan to version 3.11.0 or later, which correctly verifies the cryptographic signature of OCSP responses during X.509 path validation. Organizations unable to upgrade immediately should consider implementing network controls to restrict and monitor OCSP HTTP traffic, and may evaluate certificate pinning or alternative revocation mechanisms (e.g., CRL-based validation) as interim mitigations. Applications using Botan 2.x are not affected by this vulnerability (GitHub Advisory).

The vulnerability was reported to the Botan project by researcher HarutoKimura and was published as a GitHub Security Advisory (GHSA-9j2j-hqmc-hf5x) by the maintainer (randombit) on March 29, 2026. Coverage has appeared on security aggregation sites and Linux community forums, including a mention in a Solus Linux weekly security digest and a German Linux security news outlet (pro-linux.de), indicating moderate community awareness. No major vendor statements or significant social media controversy have been identified beyond standard vulnerability disclosure channels (GitHub Advisory).