Cyber Resilience

CVE-2026-82481

Published
29 August 2026
Modified
01 September 2026
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:A/V:D/RE:M/U:X
EPSS Score 0.0050 42th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-82481 is a high-severity Incorrect Behavior Order: Validate Before Canonicalize (CWE-180) vulnerability. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Obfuscated Files or Information (T1027); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

The cohttp package before 6.3.0 for OCaml allows directory traversal.

CWE(s)
CWE-180

Related Threats

MITRE ATT&CK Enterprise Techniques

T1027 Obfuscated Files or Information Stealth
Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-43716Shared CWE-180
CVE-2025-33194Shared CWE-180
CVE-2026-34786Shared CWE-180
CVE-2026-7120Shared CWE-180
CVE-2026-39409Shared CWE-180
CVE-2024-28607Shared CWE-180
CVE-2026-34475Shared CWE-180
CVE-2026-24895Shared CWE-180
CVE-2026-73420Shared CWE-180
CVE-2026-52747Shared CWE-180

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.8
  • V1.1.1
  • V12.1.3

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

SA-11 requires developer testing and evaluation that can discover validation-order defects after they have been coded.

SI-10 Information Input Validation good match

SI-10 requires validity checks on inputs; when implemented with canonicalization preceding validation it structurally prevents the exact ordering flaw.

SA-8 Security and Privacy Engineering Principles partial match

SA-8 mandates security engineering principles that include correct canonicalization-before-validation ordering for input handling.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
prevents

Secure SDLC practices directly require correct validation order after canonicalization to prevent bypasses.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and canonicalization order, directly addressing CWE-180.

A.8.26 Application security requirements partial match
prevents

Application security requirements include proper input handling to prevent validation-before-canonicalization flaws.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of ordering errors in input processing.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require canonicalize-then-validate to eliminate CWE-180.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing can detect validation-order defects before deployment.

References