CVE-2026-48057: randombit botan · Improper Certificate Validation
Affects randombit botanSource CVE Database V5
Not known to be exploited · CVSS 2.1 Low : upgrade to 3.13.0 when convenient.
Data as of 6 Nov 2026, 21:35 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 2.1 |
|---|
- Patch
- Available – fixed in 3.13.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 6 Nov 2026.
What to do
Upgrade randombit botan to 3.13.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| randombitbotan | Affected
| Fixed in
|
AI-suggested
Upgrade Botan to version 3.13.0 or later, where this improper certificate validation issue is fixed. No other mitigations are indicated or required.
Description
CVE-2026-48057 is a low-severity vulnerability in the Botan C++ cryptography library prior to version 3.13.0. It involves improper certificate validation due to flawed handling of multi-value Relative Distinguished Names (RDNs) in X.509 Distinguished Name decoding. An attacker controlling a name-constrained intermediate CA can exploit this to bypass DN name constraints when certificates lack a subjectAlternativeName extension. This issue is fixed in Botan version 3.13.0.