Improper Certificate Validation Affecting botan3 package, versions <3.11.0+dfsg-2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.16% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN13-BOTAN3-15928811
  • published8 Apr 2026
  • disclosed30 Mar 2026

Introduced: 30 Mar 2026

CVE-2026-32884  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade Debian:13 botan3 to version 3.11.0+dfsg-2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream botan3 package and not the botan3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1