Botan1.10: Prior to version 3.11.0, during processing of an X.509 certificate path using name constraints which
Affects botan1.10Source GCVE Database
Not known to be exploited · CVSS 5.9 Medium · fixed in 3.11.0 : update botan1.10 when convenient.
Data as of 17 Nov 2026, 20:36 UTC
- 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:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Mar 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10botan3pkg:deb/ubuntu/botan3?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSbotan3pkg:deb/ubuntu/botan3?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 25.10botanpkg:deb/ubuntu/botan?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10botan3pkg:deb/ubuntu/botan3?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu Pro 24.04 LTSbotanpkg:deb/ubuntu/botan?arch=source&distro=esm-apps/nobleOther threats | Affected
| Fixed in– |
Ubuntu Pro 22.04 LTSbotanpkg:deb/ubuntu/botan?arch=source&distro=esm-apps/jammyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Botan is a C++ cryptography library. Prior to version 3.11.0, during processing of an X.509 certificate path using name constraints which restrict the set of allowable DNS names, if no subject alternative name is defined in the end-entity certificate Botan would check that the CN was allowed by the DNS name constraints, even though this check is technically not required by RFC 5280. However this check failed to account for the possibility of a mixed-case CN. Thus a certificate with CN=Sub.EVIL.COM and no subject alternative name would bypasses an excludedSubtrees constraint for evil.com because the comparison is case-sensitive. This issue has been patched in version 3.11.0.