https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 04:24:49 +0000 https://vulnerability.circl.lu/vuln/bdu:2026-09630 bdu:2026-09630 https://vulnerability.circl.lu/vuln/bdu:2026-09630 https://vulnerability.circl.lu/vuln/fkie_cve-2026-32884 <p>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.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-32884 https://vulnerability.circl.lu/vuln/opensuse-su-2026:20566-1 <p>Security update for Botan</p> <p>Security update for Botan</p> https://vulnerability.circl.lu/vuln/opensuse-su-2026:20566-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-32884 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: botan1.10, Ubuntu:16.04:LTS: botan1.10, Ubuntu:18.04:LTS: botan, Ubuntu:18.04:LTS: botan1.10, Ubuntu:20.04:LTS: botan, Ubuntu:Pro:22.04:LTS: botan, Ubuntu:Pro:24.04:LTS: botan, Ubuntu:25.10: botan, Ubuntu:25.10: botan3, Ubuntu:26.04:LTS: botan3</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: botan1.10, Ubuntu:16.04:LTS: botan1.10, Ubuntu:18.04:LTS: botan, Ubuntu:18.04:LTS: botan1.10, Ubuntu:20.04:LTS: botan, Ubuntu:Pro:22.04:LTS: botan, Ubuntu:Pro:24.04:LTS: botan, Ubuntu:25.10: botan, Ubuntu:25.10: botan3, Ubuntu:26.04:LTS: botan3</p> <p>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.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-32884