In OCaml opam before 2.5.1, a .install field containing a destination filepath can use ../ to reach a parent directory.
CVE-2026-41082
This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EG Risk
- 51(Track)EG Risk 51/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 computedSeverity78% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
April 16, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jun 14, 2026[SECURITY] [DLA 4541-1] opam security update
https://lists.debian.org/debian-lts-announce/2026/04/msg00021.html2.5.1
Patch available: ocaml/opam 2.5.1
https://github.com/ocaml/opam/releases/tag/2.5.1Invalidate .install fields containing destination filepath trying to escape their scope
Fix merged in ocaml/opam PR #6897 on 2026-04-15 — awaiting tagged release
https://github.com/ocaml/opam/pull/6897Vendor Advisories for CVE-2026-41082(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-41082Microsoft Security Response Center (MSRC)High
In OCaml opam before 2.5.1, a .install field containing a destination filepath can use ../ to reach a parent directory.
- GHSA-97q5-qf47-hvrwGitHub Security AdvisoriesHigh
In OCaml opam before 2.5.1, a .install field containing a destination filepath can use ../ to...
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | opam-installer (2.1.5-1ubuntu0.1~esm2) @ noble | 2026-06-14 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| opam | 2.0.8-1 | 2.0.8-1+deb11u1 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| opam | 2.1.2-1 | 2.1.2-1+deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| opam | 2.3.0-1 | 2.3.0-1+deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| opam | 2.3.0-1, 2.4.1-1, 2.5.0-1 | 2.5.1-1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 7× in last 7d / 26× 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.
Showing the most recent 100 of 209 total refreshes for this CVE.
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 04:58 UTCOSV refresh
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 06:34 UTCEG score recompute
- 2026-08-16 06:34 UTCVendor advisory
- 2026-08-16 06:34 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 18:08 UTCVendor advisory
- 2026-08-14 18:08 UTCGHSA enrichment
- 2026-08-14 04:40 UTCEG score recompute
- 2026-08-14 04:40 UTCVendor advisory
- 2026-08-14 04:40 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 08:54 UTCVendor advisory
- 2026-08-13 08:54 UTCGHSA enrichment
- 2026-08-12 18:50 UTCEG score recompute
- 2026-08-12 18:50 UTCVendor advisory
- 2026-08-12 18:50 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 17:00 UTCEG score recompute
- 2026-08-11 17:00 UTCVendor advisory
- 2026-08-11 16:59 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 02:35 UTCEG score recompute
- 2026-08-11 02:35 UTCVendor advisory
- 2026-08-11 02:35 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 05:22 UTCVendor advisory
- 2026-08-10 05:22 UTCGHSA enrichment
- 2026-08-09 16:40 UTCEG score recompute
- 2026-08-09 16:40 UTCVendor advisory
- 2026-08-09 16:39 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 03:57 UTCEG score recompute
- 2026-08-09 03:57 UTCVendor advisory
- 2026-08-09 03:57 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 02:04 UTCEG score recompute
- 2026-08-08 02:04 UTCVendor advisory
- 2026-08-08 02:04 UTCGHSA enrichment
- 2026-08-07 13:22 UTCEG score recompute
- 2026-08-07 13:22 UTCVendor advisory
- 2026-08-07 13:22 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 12:06 UTCVendor advisory
- 2026-08-06 12:06 UTCGHSA enrichment
- 2026-08-05 23:20 UTCEG score recompute
- 2026-08-05 23:20 UTCVendor advisory
- 2026-08-05 23:20 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 21:33 UTCEG score recompute
- 2026-08-03 21:33 UTCVendor advisory
- 2026-08-03 21:33 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 01:52 UTCVendor advisory
- 2026-08-03 01:52 UTCGHSA enrichment
- 2026-08-02 13:10 UTCEG score recompute
- 2026-08-02 13:10 UTCVendor advisory
- 2026-08-02 13:10 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:11 UTCEG score recompute▲ 0.50
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-41082?
When was CVE-2026-41082 disclosed?
Is CVE-2026-41082 actively exploited?
What is the CVSS score of CVE-2026-41082?
How do I remediate CVE-2026-41082?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41082
Is Your Infrastructure Affected by CVE-2026-41082?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.