CVE-2026-82481

HIGHPre-NVD 8.78.7
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The cohttp package before 6.3.0 for OCaml allows directory traversal.

CVSS v3
8.7
EG Score
8.7(low)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

August 29, 2026

Last Modified

August 29, 2026

Advisory Details (1)

Auto-updated Aug 29, 2026
Patch available. Sources: github_pr.
github_pr 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 4× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 02:53 UTCGHSA enrichment
  2. 2026-08-29 15:24 UTCEG score recompute
  3. 2026-08-29 14:49 UTCEG score recompute
  4. 2026-08-29 14:47 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-82481?
CVE-2026-82481 is a high vulnerability published on August 29, 2026. The cohttp package before 6.3.0 for OCaml allows directory traversal.
When was CVE-2026-82481 disclosed?
CVE-2026-82481 was first published in the National Vulnerability Database on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-82481?
CVE-2026-82481 has a CVSS v3 base score of 8.7 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-82481?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82481, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs