botan project botan

Name: botan project botan
Brand: botan project

productUS

cpe:2.3:a:botan_project:botan:*:*:*:*:*:*:*:*

A product tracked in the threat graph; the vulnerabilities below are known to affect it.

KEV-listed

public exploit

EPSS ≥ 10%

by severity

10critical15high6medium0low

updated 2026-10-28

vulnerabilities (35)

Related CVEs.

sort

ID	severity	EPSS	exploitable	patched	published	affected
CVE-2016-2195US	critical9.8	6.68% (94th)	—	no fix	2016-05-13	28 versions
CVE-2016-2196US	critical9.8	5.34% (93rd)	—	no fix	2016-05-13	27 versions
CVE-2016-2849US	high7.5	2.81% (86th)	—	no fix	2016-05-13	30 versions
CVE-2016-2194US	high7.5	2.56% (85th)	—	no fix	2016-05-13	28 versions
CVE-2015-7827US	high7.5	2.44% (84th)	—	no fix	2016-05-13	23 versions
CVE-2016-9132US	critical9.8	2.32% (83rd)	—	no fix	2017-01-30	84 versions
CVE-2016-2850US	high7.5	2.12% (82nd)	—	no fix	2016-05-13	29 versions
CVE-2021-24115US	critical9.8OT elevated	1.92% (80th)	—	2.17.3	2021-02-22	< 2.17.3
CVE-2015-7824US	high7.5	1.69% (77th)	—	no fix	2017-04-10	≤ 1.11.21
CVE-2021-40529US	medium5.9OT elevated	1.53% (75th)	—	no fix	2021-09-06	≤ 2.18.1
CVE-2018-20187US	medium5.9	1.52% (75th)	—	2.9.0	2019-03-08	< 2.9.0
CVE-2015-5727US	high7.5	1.48% (74th)	—	no fix	2016-05-13	29 versions
CVE-2014-9742US	high7.5	1.43% (73rd)	—	no fix	2016-05-13	10 versions
CVE-2018-9860US	high7.5	1.36% (71st)	—	2.6.0	2018-04-12	1.11.32 → 2.6.0
CVE-2015-5726US	high7.5	1.35% (71st)	—	no fix	2016-05-13	29 versions
CVE-2017-2801US	critical9.8	1.32% (71st)	—	no fix	2017-05-24	= 2.0.1
CVE-2016-6878US	critical9.8	1.23% (69th)	—	no fix	2017-04-10	≤ 1.11.30
CVE-2015-7826US	critical9.8	1.11% (66th)	—	no fix	2017-04-10	≤ 1.11.21
CVE-2015-7825US	high7.5	1.04% (64th)	—	no fix	2017-04-10	≤ 1.11.21
CVE-2018-9127US	critical9.8	0.93% (60th)	—	no fix	2018-04-02	2.2.0 → 2.4.0
CVE-2016-6879US	high7.5	0.56% (46th)	—	no fix	2017-04-10	31 versions
CVE-2024-50383US	—	0.55% (46th)	—	3.6.0	2024-10-23	< 3.6.0
CVE-2024-50382US	—	0.55% (46th)	—	3.6.0	2024-10-23	< 3.6.0
CVE-2018-12435US	medium5.9	0.49% (42nd)	—	no fix	2018-06-15	2.5.0 → 2.7.0
CVE-2026-34580US	high7.5	0.45% (39th)	—	no fix	2026-04-07	= 3.11.0
CVE-2022-43705US	critical9.1	0.45% (39th)	—	2.19.3	2022-11-27	1.11.34 → 2.19.3
CVE-2016-8871US	medium6.2	0.41% (35th)	—	no fix	2016-10-28	4 versions
CVE-2026-44378US	high7.5	0.32% (25th)	—	3.12.0	2026-05-27	< 3.12.0
CVE-2017-14737US	medium5.5	0.32% (25th)	—	no fix	2017-09-26	36 versions
CVE-2017-7252US	high7.5OT elevated	0.32% (24th)	—	2.1.0	2023-11-03	1.11.0 → 2.1.0
CVE-2026-32877US	high8.2	0.29% (21st)	—	3.11.0	2026-03-30	2.3.0 → 3.11.0
CVE-2024-39312US	medium5.3	0.27% (19th)	—	2.19.5	2024-07-08	2 versions
CVE-2026-34582US	critical9.1	0.23% (14th)	—	no fix	2026-04-07	3.0.0 → 3.11.0
CVE-2026-32884US	—	0.17% (6th)	—	3.11.0	2026-03-30	< 3.11.0
CVE-2026-32883US	—	0.16% (5th)	—	3.11.0	2026-03-30	3.0.0 → 3.11.0

weaknesses (8)

The flaw types (CWEs) most of these CVEs share.

CWE-295Improper Certificate Validation6 CVEs
CWE-200Exposure of Sensitive Information to an Unauthorized Actor5 CVEs
CWE-20Improper Input Validation4 CVEs
CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer2 CVEs
CWE-125Out-of-bounds Read2 CVEs
CWE-203Observable Discrepancy2 CVEs
CWE-320CWE-3202 CVEs
CWE-327Use of a Broken or Risky Cryptographic Algorithm2 CVEs

sources (1)

Which sources assert this record, and when.

USNVD / CVE35 CVEs

scry

Products carry known vulnerabilities once they are exposed to the internet. See what is exposed on your perimeter with a free passive scan.

Free scan