Quick answers
- Is CVE-2026-118765 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118765 being exploited in the wild.
- How severe is CVE-2026-118765?
- Informational severity, published 29 October 2026.
- Which products and versions are affected?
- Botan 3.7.0 to 3.13.0.
- Is there a fix for CVE-2026-118765?
- 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-118765 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-118765?
- 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
In Botan versions 3.7.0 through 3.13.0, the AutoSeeded_RNG::fill_bytes_with_input() method does not properly validate empty output buffers before seeding, causing the generator to transition to a seeded state without consulting configured entropy sources. On builds lacking BOTAN_HAS_SYSTEM_RNG, this results in reliance on only clock values and process IDs as entropy, producing predictable output. The fix checks for both empty output and input buffers before transitioning to seeded state.
Affected products
- Botan Botan 3.7.0 to 3.13.0
Timeline
- 2026-10-29: disclosed