Threat Intelligence Database

CVE-2026-44378 is a medium severity vulnerability in the Botan C++ cryptography library prior to version 3.12.0. It involves inefficient algorithmic complexity in parsing certain indefinite length BER encodings, which can cause quadratic parsing behavior leading to denial of service. The vulnerability arises because Botan accepted indefinite length encodings in structures that should be DER encoded, which prohibits such encodings. This issue is fixed in Botan version 3.12.0.

Botan is a C++ cryptography library. Prior to version 3.11.1, the TLS 1.3 implementation allowed ApplicationData records to be processed prior to the Finished message being received. A server which is attempting to enforce client authentication via certificates can by bypassed by a client which entirely omits Certificate, CertificateVerify, and the Finished message and instead sends application data records. This vulnerability is fixed in 3.11.1.

Botan is a C++ cryptography library. In 3.11.0, the function Certificate_Store::certificate_known had a misleading name; it would return true if any certificate in the store had a DN (and subject key identifier, if set) matching that of the argument. It did not check that the cert it found and the cert it was passed were actually the same certificate. In 3.11.0 an extension of path validation logic was made which assumed that certificate_known only returned true if the certificates were in fact identical. The impact is that if an end entity certificate is presented, and its DN (and subject key identifier, if set) match that of any trusted root, the end entity certificate is accepted immediately as if it itself were a trusted root. , This vulnerability is fixed in 3.11.1.

CVE-2026-32877 is a high-severity vulnerability in the Botan C++ cryptography library versions 2.3.0 up to but not including 3.11.0. The issue occurs during SM2 decryption where the authentication code (C3) length is not properly validated before comparison. This can lead to an out-of-bounds heap read of up to 31 bytes when processing invalid ciphertexts, potentially causing a crash or other undefined behavior. The vulnerability has been addressed in Botan version 3.11.0.

Botan is a C++ cryptography library. From version 3.0.0 to before version 3.11.0, during X509 path validation, OCSP responses were checked for an appropriate status code, but critically omitted verifying the signature of the OCSP response itself. This issue has been patched in version 3.11.0.

CVE-2026-32884 is a medium severity vulnerability in the Botan C++ cryptography library prior to version 3.11.0. The issue involves improper certificate validation related to name constraints in X.509 certificate path processing. Specifically, when an end-entity certificate lacks a subject alternative name (SAN), Botan checked the common name (CN) against DNS name constraints in a case-sensitive manner, which is not required by RFC 5280. This allowed certificates with mixed-case CN values to bypass excludedSubtrees constraints, potentially permitting unauthorized certificates to be accepted. The vulnerability has been patched in Botan version 3.11.0.

Botan before 3.6.0, when certain GCC versions are used, has a compiler-induced secret-dependent operation in lib/utils/donna128.h in donna128 (used in Chacha-Poly1305 and x25519). An addition can be skipped if a carry is not set. This was observed for GCC 11.3.0 with -O2 on MIPS, and GCC on x86-i386. (Only 32-bit processors can be affected.)

MediumVulnerabilityUnited StatesChinaRussia+7#cve#cve-2024-50383

Botan before 3.6.0, when certain LLVM versions are used, has compiler-induced secret-dependent control flow in lib/utils/ghash/ghash.cpp in GHASH in AES-GCM. There is a branch instead of an XOR with carry. This was observed for Clang in LLVM 15 on RISC-V.

MediumVulnerabilityUnited StatesChinaGermany+7#cve#cve-2024-50382

Botan is a C++ cryptography library. X.509 certificates can identify elliptic curves using either an object identifier or using explicit encoding of the parameters. Prior to versions 3.3.0 and 2.19.4, an attacker could present an ECDSA X.509 certificate using explicit encoding where the parameters are very large. The proof of concept used a 16Kbit prime for this purpose. When parsing, the parameter is checked to be prime, causing excessive computation. This was patched in 2.19.4 and 3.3.0 to allow the prime parameter of the elliptic curve to be at most 521 bits. No known workarounds are available. Note that support for explicit encoding of elliptic curve parameters is deprecated in Botan.

HighVulnerabilityGermanyFranceUnited Kingdom+7#cve#cve-2024-34703#cwe-405