Live › vulnerability › CVE-2026-118765
Botan is a C++ cryptography library. From 3.7.0 to 3.13.0, calling AutoSeeded_RNG::clear() then randomize with an empty buffer can mark the generator seeded without real entropy, so later output can be predictable on builds without a system RNG.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 17:26 UTC. All times on this page are UTC.
Applications that use Botan 3.7.0 through 3.13.0 and call AutoSeeded_RNG::clear() followed by randomize with an empty output buffer. The problem appears on builds without BOTAN_HAS_SYSTEM_RNG, where the fallback seed uses only a clock value and process ID. Applications on other versions, or that never clear the generator, can skip it.
No product ranges from the sources yet.
botan version or the package manager listing.AutoSeeded_RNG::clear() followed by randomize in the application code.3.13.0Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-118765")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.