CVE-2026-118768

Botan: CLI utility `ocsp_check` accepts unauthenticated responses

Published Oct 29, 2026 CVSS 4.0 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
Botan is a C++ cryptography library. From 1.11.34 until 3.13.0, the botan ocsp_check command requested an OCSP response from a certificate's Authority Information Access URL without verifying the response signature or authorizing the signer. A malicious responder or on-path attacker could return a matching and timely GOOD response with an empty, invalid, or unauthorized signature, causing a revoked certificate to produce exit status 0 and OCSP check OK output. Only the command-line interface is affected. This issue is fixed in version 3.13.0.

Analysis

AI-generated

Technical impact

Botan’s ocsp_check utility in versions 1.11.34 through 3.13.0 does not verify the authenticity of OCSP responses it receives. A responder that returns a timely GOOD response with an empty, invalid, or unsigned signature can make a revoked certificate appear valid. The weakness, documented as CWE‑347, allows an attacker to bypass revocation checks by tricking the tool into accepting an unauthenticated response, potentially leading to the use of a compromised or revoked credential.

Affected Systems

The vulnerability affects the RandomBit Botan cryptographic library, specifically the command‑line ocsp_check tool. Versions from 1.11.34 up to, but not including, 3.13.0 are impacted. Only the CLI is affected; library code used by applications is not vulnerable.

Risk and Exploitability

The CVSS score of 5.9 indicates moderate severity. No EPSS score is available, and the issue is not listed in the CISA KEV catalog. Exploitation requires control of an OCSP responder or an attacker on the network path to supply a forged response. Because the flaw is in a standalone command‑line tool, the practical attack surface is limited to environments that rely on ocsp_check for certificate verification. However, failure to detect a revoked certificate can lead to misuse of the certificate in downstream applications.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to botan 3.13.0 or later, which adds OCI response signature verification
  • If an upgrade is not immediately possible, disable OCSP checking in the ocsp_check command or manually validate responses before accepting them
  • Configure the environment to block untrusted OCSP responders or use a trusted, authenticated responder

Generated by OpenCVE AI on October 29, 2026 at 18:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N'}

threat_severity

Moderate

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Randombit
Randombit botan
Vendors & Products Randombit
Randombit botan
Type Values Removed Values Added
Description Botan is a C++ cryptography library. From 1.11.34 until 3.13.0, the botan ocsp_check command requested an OCSP response from a certificate's Authority Information Access URL without verifying the response signature or authorizing the signer. A malicious responder or on-path attacker could return a matching and timely GOOD response with an empty, invalid, or unauthorized signature, causing a revoked certificate to produce exit status 0 and OCSP check OK output. Only the command-line interface is affected. This issue is fixed in version 3.13.0.
Title Botan: CLI utility `ocsp_check` accepts unauthenticated responses
Weaknesses CWE-347
References
Metrics cvssV4_0

{'score': 5.9, 'vector': 'CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 3, 2026, 4:06 PM
Reserved
Oct 28, 2026, 7:20 PM
Status
Awaiting Analysis
Published
Oct 29, 2026, 6:17 PM
Modified
Nov 3, 2026, 5:17 PM
Severity
Moderate
Public date
Oct 29, 2026, 5:20 PM