CVE-2026-118765: high-severity vulnerability in randombit botan
Botan: AutoSeeded_RNG can become reinitialized from predictable data after clearing state
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.3epss 0.1%
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.
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
Affected products
randombit · botanRelated CVEs — randombit botan
In the same product, most dangerous first.
CVE-2024-34702MEDIUMBotan has a Denial of Service Due to Excessive Name ConstraintsEPSS 0.8%CVE-2024-34703HIGHBotan Vulnerable to Denial of Service Due to Overly Large Elliptic Curve ParametersEPSS 0.5%CVE-2026-34580CRITICALBotan has a certificate authentication bypass due to trust anchor confusionEPSS 0.5%CVE-2026-118769CRITICALBotan: Integer overflow when reporting block size in FFI can cause memory corruptionEPSS 0.4%CVE-2026-44378MEDIUMBotan: Quadratic complexity decoding BER indefinite length encodingsEPSS 0.3%CVE-2026-32877HIGHBotan: Heap Buffer Over-read in SM2 Decryption via Undersized C3 Hash FieldEPSS 0.3%