Predictive Vulnerability Intelligence.

Product

  • Product
  • Pricing
  • Documentation

Company

  • About
  • Partnerships
  • Blog
  • Support

Legal

  • Terms
  • Privacy
  • Data Licensing

© 2026 FAUCET Technologies LLC. All rights reserved.

Botan Project

First CVE: May 13, 2016Active for: 10 yearsTotal CVEs: 35
45.8
VTI Score
High

Botan Project maintains a cryptographic library widely embedded across server applications and security-sensitive infrastructure, despite its focused product scope. Vulnerabilities affecting the vendor skew strongly toward critical-severity outcomes, reflecting the cryptographic and certificate-handling operations that anchor the library's role in authentication and encryption workflows. The recurring exposure centers on weakness classes including improper certificate validation, information disclosure, and memory-safety issues such as buffer overflows and improper input validation, each of which can undermine the trust guarantees that dependent applications rely upon. Defenders should treat Botan library updates as high-priority, particularly when the vendor publishes fixes for certificate-validation or authentication-layer flaws, and should inventory downstream products that embed this library rather than tracking the library in isolation. Current severity, exploitation activity, and exposure counts are shown alongside this summary.

FAUCET AI Generated
35
Total CVEs
More Total CVEs than 98% of tracked vendors
3.9
Avg CVEs / Product / Year
More Avg CVEs / Product / Year than 95% of tracked vendors
7.7
Avg CVSS Score
Higher Avg CVSS Score than 73% of tracked vendors
0.0%
In CISA KEV
Bottom 1%

Trends Over Time

The number and severity of CVEs published that impact products developed by Botan Project over time

Volume of CVEsAvg CVSS Base Score
First CVE
May 13, 2016
10 years ago
Most Recent CVE
May 27, 2026
58 days ago

Products(1 total)

Top CVEs

Signals from CVEs in this vendor scope (35 CVEs).

35 CVEs · Highest risk first

CVEPublishedCVSSRiskKEVExploit
CVE-2016-2195CRITICAL
Integer overflow in the PointGFp constructor in Botan before 1.10.11 and 1.11.x before 1.11.27 allows remote attackers to overwrite memory and possibly execute arbitrary code via a
May 13, 20169.832NONO
CVE-2026-34582CRITICAL
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 receive
Apr 7, 20269.131NONO
CVE-2016-6878CRITICAL
The Curve25519 code in botan before 1.11.31, on systems without a native 128-bit integer type, might allow attackers to have unspecified impact via vectors related to undefined beh
Apr 10, 20179.831NONO
CVE-2016-2196CRITICAL
Heap-based buffer overflow in the P-521 reduction function in Botan 1.11.x before 1.11.27 allows remote attackers to cause a denial of service (memory overwrite and crash) or execu
May 13, 20169.831NONO
CVE-2021-24115CRITICAL
In Botan before 2.17.3, constant-time computations are not used for certain decoding and encoding operations (base32, base58, base64, and hex).
Feb 22, 20219.830NONO
CVE-2016-9132CRITICAL
In Botan 1.8.0 through 1.11.33, when decoding BER data an integer overflow could occur, which would cause an incorrect length field to be computed. Some API callers may use the ret
Jan 30, 20179.830NONO
CVE-2022-43705CRITICAL
In Botan before 2.19.3, it is possible to forge OCSP responses due to a certificate verification error. This issue was introduced in Botan 1.11.34 (November 2016).
Nov 27, 20229.129NONO
CVE-2015-7826CRITICAL
botan 1.11.x before 1.11.22 improperly handles wildcard matching against hostnames, which might allow remote attackers to have unspecified impact via a valid X.509 certificate, as
Apr 10, 20179.829NONO
CVE-2026-34580HIGH
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
Apr 7, 20267.528NONO
CVE-2026-32877HIGH
Botan is a C++ cryptography library. From version 2.3.0 to before version 3.11.0, during SM2 decryption, the code that checked the authentication code value (C3) failed to check th
Mar 30, 20268.228NONO
View all 35 CVEs →

CVE Severity & Scoring

Severity distribution of CVEs that affect this vendor's products35 CVEs
29%
43%
29%
Severity distribution among all CVEs352,231 CVEs
45%
40%
11%
MediumHighCritical
Attack Vector
Local3 (8.6%)
Network32 (91.4%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low28 (80.0%)
High7 (20.0%)
Unknown0 (0.0%)
User Interaction
None35 (100.0%)
Unknown0 (0.0%)
Required0 (0.0%)
Privileges Required
Low1 (2.9%)
High0 (0.0%)
None34 (97.1%)
Unknown0 (0.0%)

Exploit Exposure

Signals from CVEs in this vendor scope (35 CVEs).

CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%

Social Chatter

An overview of all social media posts that mention a CVE ID that affects a product developed by Botan Project.

Media Mentions

Media articles that mention a CVE ID that affects a product developed by Botan Project — matched by CVE ID, not by vendor name.

Top CNAs Publishing CVEs For Botan Project's Products

View all 3 CNAs →

Top CWEs