# CVE-2026-118765: Botan: AutoSeeded_RNG can become reinitialized from predictable data after clearing state


- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/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-95xx-xh9v-v9c4

## What is CVE-2026-118765?

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

### Official description

Botan is a C++ cryptography library. From 3.7.0 until 3.13.0, an application that calls AutoSeeded_RNG::clear() and then calls randomize with an empty output buffer while the generator is unseeded can cause AutoSeeded_RNG to mark itself seeded without consulting the configured entropy source. On builds without BOTAN_HAS_SYSTEM_RNG, the fallback uses only a clock value and process ID, so a later non-empty request can produce output from predictable state. This issue is fixed in version 3.13.0.

Weakness: CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG))

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


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

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

## Is CVE-2026-118765 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118765 is a high-severity vulnerability in randombit botan, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118765 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-118765/ (Markdown: https://insights.sbomify.com/CVE-2026-118765/index.md)
```

## Sources

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

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