# CVE-2026-118768: Botan: CLI utility `ocsp_check` accepts unauthenticated responses


- **Severity:** Medium 5.9 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-mpr7-9494-4qcw

## What is CVE-2026-118768?

CVE-2026-118768 is a medium-severity vulnerability in randombit botan, published on 29 Oct 2026. 

### Official 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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-118768?


## How do I fix CVE-2026-118768?

No fix has been published for CVE-2026-118768 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118768 being exploited?

There is no known exploitation of CVE-2026-118768 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118768 and fix it if it is affected.

What it is: CVE-2026-118768 is a medium-severity vulnerability in randombit botan, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118768 in the wild and no public exploit code.

Affected product: randombit botan. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-118768/ (Markdown: https://insights.sbomify.com/CVE-2026-118768/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118768
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118768
- OSV: https://osv.dev/vulnerability/CVE-2026-118768

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118768/
Summaries are generated and may contain mistakes; the official description above is the record.