Botan is a C++ cryptography library. From 1.11.34 until 3.13.0, the botan ocsp_check command requested an OCSP response from a certificate's Authority Information Access URL without verifying the response signature or authorizing the signer. A malicious responder or on-path attacker could return a matching and timely GOOD response with an empty, invalid, or unauthorized signature, causing a revoked certificate to produce exit status 0 and OCSP check OK output. Only the command-line interface is affected. This issue is fixed in version 3.13.0.
CVE-2026-118768
MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: <0.1% (below the 1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-113277 (ENISA EUVD)Source: ENISA EUVD
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 5.9Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS
- 5.9
- EG Score
- 5.9MEDIUMmedium confidence
- EG Risk
- 27EG Risk 27/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity59% × 45%Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation<0.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- <0.1%
- EPSS %ILE
- below the 1st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
- EG Likelihood
- <0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 29, 2026
Last Modified
November 3, 2026
Advisory Details (3)
Auto-updated Oct 29, 2026Patch available. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)
CLI utility `ocsp_check` accepts unauthenticated responses · Advisory · randombit/botan · GitHub
https://github.com/randombit/botan/security/advisories/GHSA-mpr7-9494-4qcwGitHub pull request
Authenticate OCSP responses in ocsp_check
Fix merged in randombit/botan PR #5825 on 2026-08-08 — awaiting tagged release
https://github.com/randombit/botan/pull/5825GitHub commit
commit 46b2a9ca59b0 (randombit/botan)
Fix landed in randombit/botan commit 46b2a9ca59b0 — awaiting tagged release
https://github.com/randombit/botan/commit/46b2a9ca59b0797184fbf7537495bda6e61a1983Affected Packages
(4 across 3 ecosystems)
Debian:13(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| botan | 2.19.5+dfsg-4 |
| — |
| botan3 | 3.10.0+dfsg-1 ... 3.9.0+dfsg-2.1 (15 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| botan | 2.19.3+dfsg-1 ... 2.19.5+dfsg-4 (7 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| botan3 | 3.10.0+dfsg-1 ... 3.9.0+dfsg-2.1 (14 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 8× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-11 16:38 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-11-11 06:56 UTCEchelonGraph re-scored
- 2026-11-10 16:42 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-11-04 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-11-03 17:26 UTCEchelonGraph re-scored
- 2026-11-03 16:20 UTCEchelonGraph re-scored
- 2026-10-31 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-30 19:47 UTCEchelonGraph re-scored
- 2026-10-30 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-29 18:27 UTCEchelonGraph re-scored
- 2026-10-29 18:02 UTCENISA EUVD ID recordedEUVD-2026-113277 · Source: ENISA EUVD
- 2026-10-29 17:27 UTCEchelonGraph re-scoredFirst assessed: 5.9 MEDIUM
- 2026-10-29 17:27 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownDebian:13:botan3
Frequently asked(5)
What is CVE-2026-118768?
CVE-2026-118768 is a medium-severity vulnerability; its CVE record was published on October 29, 2026. Botan is a C++ cryptography library. From 1.11.34 until 3.13.0, the botan ocsp_check command requested an OCSP response from a certificate's Authority Information Access URL without verifying the response signature or authorizing the signer. A malicious responder or on-path attacker could return a…
When was the CVE record for CVE-2026-118768 published?
The CVE record for CVE-2026-118768 was published on October 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-118768 actively exploited?
CVE-2026-118768 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118768?
CVE-2026-118768 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-118768?
A fix for CVE-2026-118768 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-118768
Is Your Infrastructure Affected by CVE-2026-118768?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.