Skip to main content
VulnerabilityPublished

CVE-2026-32877: randombit botan · Out-of-bounds Read

Affects randombit botanSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 3.11.0 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.11.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade botan and randombit/botan to 3.11.0.

Affected software

ProductAffectedFixed in
randombitbotanAffected
  • >=2.3.0 <3.11.0
Fixed in
  • 3.11.0
GitHubrandombit/botanpkg:github/randombit/botanOther threatsAffected
  • >=2.3.0 <3.11.0
Fixed in
  • 3.11.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Botan version 3.11.0 or later, where this vulnerability is patched. Since this is a library vulnerability, applying the official fix by updating the library version is the recommended remediation. Patch status is confirmed by the vendor advisory stating the issue is fixed in version 3.11.0.

Description

CVE-2026-32877 is a high-severity vulnerability in the Botan C++ cryptography library versions 2.3.0 up to but not including 3.11.0. The issue occurs during SM2 decryption where the authentication code (C3) length is not properly validated before comparison. This can lead to an out-of-bounds heap read of up to 31 bytes when processing invalid ciphertexts, potentially causing a crash or other undefined behavior. The vulnerability has been addressed in Botan version 3.11.0.

References

Community reviews

Loading reviews…