cve.bz

CVE-2026-48057

2.1 lowEPSS 0.2%

Low (2.1) in randombit botan. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Botan is a C++ cryptography library. Prior to 3.13.0, Botan's X.509 Distinguished Name decoder flattens the Attribute-Value Assertions in each Relative Distinguished Name and loses multi-value RDN grouping before DN name-constraint enforcement. An attacker controlling a name-constrained intermediate CA can issue a certificate with a multi-value RDN whose first Common Name matches the permitted constraint and whose second Common Name is attacker-chosen, causing the constraint check to accept the flattened first value. If the certificate contains no subjectAlternativeName extension, the second Common Name can then be accepted as a hostname; Botan does not fall back to Common Name hostname matching when any subjectAlternativeName is present. The exposure is limited to deployments using DN name constraints, which are uncommon outside internal PKIs, and to certificates without a subjectAlternativeName. This issue is fixed in version 3.13.0.

Severity

CVSS 4.0

2.1 low
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-295 Improper Certificate Validation
CWE-1023 Incomplete Comparison with Missing Factors
OWASP Top 10
A07:2025 Authentication Failures
Published
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-48057 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48057?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48057?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-48057 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
randombit botan< 3.13.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12botanno fix listedDEBIAN-CVE-2026-48057
Debian13botan, botan3no fix listedDEBIAN-CVE-2026-48057
Debian14botan33.13.0+dfsg-2DEBIAN-CVE-2026-48057
Ubuntu18.04:LTS, 20.04:LTS, Pro:22.04:LTS and 1 morebotanno fix listedUBUNTU-CVE-2026-48057
Ubuntu26.04:LTS, 26.10botan3no fix listedUBUNTU-CVE-2026-48057
Azure Linux3botan2no fix listedAZL-112826

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON