Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:LSummary
CVE-2026-41082 is a high-severity Path Traversal: '../filedir' (CWE-24) vulnerability in Ocaml Opam. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 11th 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 AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-41082 is a path traversal vulnerability (CWE-24) in the OCaml opam package manager prior to version 2.5.1. The issue arises when processing a .install field in a package specification, which allows the destination filepath to include "../" sequences. This enables traversal to parent directories outside the intended installation scope. The vulnerability received a CVSS v3.1 base score of 7.3 (AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L), indicating high severity due to significant integrity impacts with low complexity and no privileges required.
A local attacker can exploit this vulnerability by creating or controlling a malicious opam package with a crafted .install field that uses "../" to target files in parent directories. Upon installation via opam, the package installs files to unauthorized locations, potentially overwriting critical system files. This grants high integrity disruption (I:H) with low confidentiality (C:L) and availability (A:L) impacts, all without user interaction or elevated privileges, as long as the victim runs the opam install command locally.
Mitigation involves updating to opam version 2.5.1 or later, as detailed in the official release notes and the corresponding GitHub pull request #6897 that addresses the path traversal. Debian LTS users should refer to the security announcement for patched packages in their repositories. No workarounds are specified beyond avoiding installation of untrusted packages.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23288
Vulnerability Data
In OCaml opam before 2.5.1, a .install field containing a destination filepath can use ../ to reach a parent directory.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes '../' sequences in externally-supplied pathnames before they are resolved.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
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.
Secure SDLC practices directly require input validation and path sanitization that prevent ../ traversal.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
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.
Secure coding standards require neutralizing ../ sequences and canonicalizing paths before file operations.
Security testing in development catches path-traversal flaws before release.
Secure SDLC mandates input validation and path canonicalization that directly block ../ traversal.
Application security requirements explicitly call for controls against path traversal in file-handling functions.
Secure architecture principles reduce attack surface but do not prescribe the specific coding fix.
Information access restriction limits which files can be reached, mitigating impact of traversal.