Security readout for executives and security teams
Plain-English summary
OCaml opam versions before 2.5.1 can mishandle destination paths in .install metadata. A crafted install entry may write outside the intended directory using parent-directory traversal. For businesses, the main concern is build or developer environments where package installation can alter files unexpectedly.
Executive priority
Prioritize remediation for engineering and CI environments because unexpected file writes can compromise build integrity. Treat this as high urgency where opam processes external or community packages, but avoid emergency assumptions without exposure evidence.
Technical view
This is a CWE-24 path traversal issue in opam .install destination filepath handling. The CVSS 3.1 score is 7.3: local attack vector, low complexity, no privileges, no user interaction, with high integrity impact and limited confidentiality and availability impact.
Likely exposure
Exposure is most likely where OCaml opam before 2.5.1 is installed, especially developer machines, CI runners, build workers, or package automation processing .install metadata. The source bundle’s affected-version detail is sparse, so confirm exact exposure against opam and distro advisories.
Exploitation context
The provided sources do not state active exploitation, and KEV is false. The evidence supports a local path traversal risk during opam install processing, but does not establish remote exploitation or public weaponization.
Researcher notes
The record identifies path traversal via ../ in .install destination filepaths before opam 2.5.1. Public evidence is sufficient for triage and version validation, but incomplete for exploit prevalence, vulnerable workflow prerequisites, and downstream distro patch mapping.
Mitigation direction
- Upgrade opam to 2.5.1 or later where applicable.
- Apply Debian, Red Hat, or other distribution guidance for packaged opam versions.
- Restrict untrusted package installation in CI and developer workflows.
- Review vendor advisories before assuming backported package versions are vulnerable.
Validation and detection
- Inventory opam versions on developer systems, build hosts, and CI runners.
- Check whether package install workflows consume untrusted .install metadata.
- Compare installed packages against opam 2.5.1 and distro advisory status.
- Review recent build or install anomalies involving unexpected file writes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-24: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-41082 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L2.54.7mitreCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H1.85.2redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-04-16T18:00:56.999Z: Reported to Red Hat.
- 2026-04-16T17:32:40.068Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ocaml/opam/releases/tag/2.5.1CVE reference, mitre
- https://github.com/ocaml/opam/pull/6897CVE reference, mitre
- https://osv.dev/vulnerability/OSEC-2026-03CVE reference, mitre
- https://lists.debian.org/debian-lts-announce/2026/04/msg00021.htmlCVE reference, CVE
- https://access.redhat.com/security/cve/CVE-2026-41082CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2459003CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-41082.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Path Traversal: '../filedir'
Path Traversal: '../filedir' represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.