CVE-2026-82481

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd 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-68116 (ENISA EUVD) · GHSA-qcjm-vmrx-v935 (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The cohttp package before 6.3.0 for OCaml allows directory traversal.

CVSS
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
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 (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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 low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 29, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Aug 29, 2026
Patch available. Sources: github_pr.
GitHub pull request Patch Available

cohttp: urldecode before resolving path components for files

Patch available: mirage/ocaml-cohttp v6.3.0 (PR #1145 merged 2026-08-20)

https://github.com/mirage/ocaml-cohttp/pull/1145

Vendor Advisories for CVE-2026-82481(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ocaml-cohttp4.0.0-3 ... 6.3.0-2 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ocaml-cohttp5.3.0-1 ... 6.3.0-2 (9 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ocaml-cohttp5.3.0-1 ... 6.3.0-2 (9 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 35× 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.

Showing the most recent 100 of 217 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-12 23:53 UTCEchelonGraph re-scored
  3. 2026-11-12 23:53 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  4. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-11-05 09:39 UTCEchelonGraph re-scored
  13. 2026-11-05 09:39 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  14. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  19. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-28 19:24 UTCEchelonGraph re-scored
  22. 2026-10-28 19:24 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  23. 2026-10-28 17:25 UTCOSV refresh
  24. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 75 more
  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-10-25 13:58 UTCEchelonGraph re-scored
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  6. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  8. 2026-10-20 20:17 UTCEchelonGraph re-scored
  9. 2026-10-20 20:17 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-18 03:08 UTCEchelonGraph re-scored
  14. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  18. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-10-13 06:03 UTCEchelonGraph re-scored
  20. 2026-10-13 06:02 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  21. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  22. 2026-10-12 14:55 UTCEchelonGraph re-scored
  23. 2026-10-11 19:19 UTCEchelonGraph re-scored
  24. 2026-10-11 16:36 UTCEchelonGraph re-scored
  25. 2026-10-11 13:54 UTCEchelonGraph re-scored
  26. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  28. 2026-10-10 12:14 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  29. 2026-10-10 00:45 UTCEchelonGraph re-scored
  30. 2026-10-10 00:45 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  31. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  32. 2026-10-09 02:34 UTCEchelonGraph re-scored
  33. 2026-10-09 02:34 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  34. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  35. 2026-10-08 00:45 UTCEchelonGraph re-scored
  36. 2026-10-08 00:45 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  37. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  38. 2026-10-07 06:24 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  39. 2026-10-06 18:56 UTCEchelonGraph re-scored
  40. 2026-10-06 18:55 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  41. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  42. 2026-10-06 07:27 UTCEchelonGraph re-scored
  43. 2026-10-06 07:27 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  44. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  45. 2026-10-05 16:49 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  46. 2026-10-05 04:29 UTCEchelonGraph re-scored
  47. 2026-10-05 04:29 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  48. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  49. 2026-10-04 16:44 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  50. 2026-10-04 05:15 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  51. 2026-10-03 17:46 UTCEchelonGraph re-scored
  52. 2026-10-03 17:46 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  53. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  54. 2026-10-03 06:18 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  55. 2026-10-02 18:49 UTCEchelonGraph re-scored
  56. 2026-10-02 18:49 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  57. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  58. 2026-10-02 07:16 UTCEchelonGraph re-scored
  59. 2026-10-02 07:16 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  60. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  61. 2026-10-01 19:47 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  62. 2026-10-01 07:16 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  63. 2026-09-30 19:48 UTCEchelonGraph re-scored
  64. 2026-09-30 19:48 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  65. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  66. 2026-09-30 03:48 UTCEchelonGraph re-scored
  67. 2026-09-30 03:48 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  68. 2026-09-29 08:36 UTCEchelonGraph re-scored
  69. 2026-09-29 08:36 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  70. 2026-09-28 21:07 UTCEchelonGraph re-scored
  71. 2026-09-28 21:07 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  72. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  73. 2026-09-28 06:59 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH
  74. 2026-09-27 19:28 UTCEchelonGraph re-scored
  75. 2026-09-27 19:28 UTCGHSA enrichmentGHSA-qcjm-vmrx-v935 · GitHub severity HIGH

Frequently asked(5)

What is CVE-2026-82481?
CVE-2026-82481 is a high-severity vulnerability; its CVE record was published on August 29, 2026. The cohttp package before 6.3.0 for OCaml allows directory traversal.
When was the CVE record for CVE-2026-82481 published?
The CVE record for CVE-2026-82481 was published on August 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 September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-82481 actively exploited?
CVE-2026-82481 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82481?
CVE-2026-82481 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82481?
A fix for CVE-2026-82481 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82481 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-82481

Explore →

Is Your Infrastructure Affected by CVE-2026-82481?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.