Skip to main content
VulnerabilityPublished

CVE-2026-32884: randombit botan · Improper Certificate Validation

Affects randombit botanSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 3.11.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% 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:H/PR:N/UI:N/S:U/C:N/I:H/A:N

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 30 Oct 2026.

What to do

Upgrade botan and randombit/botan to 3.11.0.

Affected software

ProductAffectedFixed in
randombitbotanAffected
  • <3.11.0
Fixed in
  • 3.11.0
GitHubrandombit/botanpkg:github/randombit/botanOther threatsAffected
  • <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

Users of Botan should upgrade to version 3.11.0 or later, where this certificate validation issue has been fixed. Since this is a library vulnerability, applying the official patch by updating the library version is the recommended remediation. There are no vendor advisories indicating that no action is required or that the issue is otherwise mitigated.

Description

CVE-2026-32884 is a medium severity vulnerability in the Botan C++ cryptography library prior to version 3.11.0. The issue involves improper certificate validation related to name constraints in X.509 certificate path processing. Specifically, when an end-entity certificate lacks a subject alternative name (SAN), Botan checked the common name (CN) against DNS name constraints in a case-sensitive manner, which is not required by RFC 5280. This allowed certificates with mixed-case CN values to bypass excludedSubtrees constraints, potentially permitting unauthorized certificates to be accepted. The vulnerability has been patched in Botan version 3.11.0.

References

Community reviews

Loading reviews…