Quick answers
- Is CVE-2026-57825 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57825 being exploited in the wild.
- How severe is CVE-2026-57825?
- Medium severity, with a CVSS score of 5.7, published 9 September 2026.
- Which products and versions are affected?
- OCaml Opam before 2.5.2.
- Is there a fix for CVE-2026-57825?
- A patch was published on 2026-07-08: opam 2.5.2 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57825 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-57825?
- Check whether you run OCaml Opam at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in opam's handling of .install files, which specify where package files should be placed during installation. The package manager fails to properly resolve and validate symlinks in target paths before installation, allowing an attacker to bypass sandbox restrictions. An attacker can craft a package that creates a symlink pointing outside the intended installation directory (e.g., to the user's home directory) and use .install file directives to write files through that symlink. The attack requires the user to install the malicious package but no additional privileges or user interaction beyond the install command. This flaw affects all opam versions before 2.5.2, which includes the fix.
Affected products
- OCaml opam before 2.5.2
Timeline
- 2026-07-07: disclosed: Vulnerability published in OSV database
- 2026-07-08: patched: opam 2.5.2 released with fix