Is CVE-2026-118768 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-118768 being exploited in the wild.

How severe is CVE-2026-118768?

Informational severity, published 29 October 2026.

Which products and versions are affected?

Botan 1.11.34 to before 3.13.0.

Is there a fix for CVE-2026-118768?

Yes: fixed in 3.13.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-118768 attacked?

It is attacked over the network or from the adjacent network, in a software library.

Am I affected by CVE-2026-118768?

Check whether you run Botan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-118768: Botan OCSP signature verification bypass in ocsp_check CLI

CVE-2026-118768 · Severity: info · Published 2026-10-29

Botan is a cryptography library used to validate SSL/TLS certificates. The ocsp_check command-line tool verifies whether certificates have been revoked by checking with an online service (OCSP). A flaw allowed attackers to forge OCSP responses that claim a revoked certificate is valid, potentially allowing use of compromised certificates. Only the command-line tool is affected; library users are not impacted.

Technologies: Botan. Vendors: Botan.

Quick answers

Is CVE-2026-118768 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-118768 being exploited in the wild.
How severe is CVE-2026-118768?: Informational severity, published 29 October 2026.
Which products and versions are affected?: Botan 1.11.34 to before 3.13.0.
Is there a fix for CVE-2026-118768?: Yes: fixed in 3.13.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-118768 attacked?: It is attacked over the network or from the adjacent network, in a software library.
Am I affected by CVE-2026-118768?: Check whether you run Botan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 3.13.0

Technical details

The ocsp_check CLI utility failed to verify OCSP response signatures or validate signer authorization, accepting any response with a matching certificate status and valid timestamp. An attacker on the network or impersonating an OCSP responder could return a forged "GOOD" response with an empty, invalid, or unauthorized signature, causing revoked certificates to validate. The fix implements cryptographic authentication via Botan::PKIX::check_ocsp().

Affected products

Botan Botan 1.11.34 to before 3.13.0

Timeline

2026-10-29: disclosed
2026-08-08: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.