CVE-2026-57825: opam for OCaml Auth Bypass Vulnerability

CVE-2026-57825 Overview

CVE-2026-57825 is a symlink handling flaw in the opam package manager for OCaml before version 2.5.2. The sandbox protection mechanism can be bypassed because symlinks are mishandled during processing of .install files. A malicious opam package can leverage this weakness to write files outside the sandbox during installation, compromising integrity on the build host. The issue is tracked under [CWE-61: UNIX Symbolic Link (Symlink) Following].

Critical Impact
A crafted opam package can escape the build sandbox through symlink manipulation in .install files, allowing arbitrary file writes with the privileges of the user running opam install.

Affected Products

opam package manager for OCaml, all versions before 2.5.2
Debian LTS distributions shipping vulnerable opam builds
Downstream OCaml build environments relying on opam sandboxing

Discovery Timeline

2026-09-09 - CVE-2026-57825 published to NVD
2026-09-09 - Last updated in NVD database

Technical Details for CVE-2026-57825

Vulnerability Analysis

opam uses a sandbox to isolate package build and install steps from the host filesystem. The sandbox restricts writes to a controlled directory tree so untrusted package definitions cannot alter arbitrary paths. This vulnerability breaks that guarantee. When opam processes .install files, it follows symbolic links without adequately validating that link targets remain inside the sandbox boundary.

A malicious package author can stage symlinks that point outside the sandbox and reference them from a .install file. When opam performs the copy or move operations described by that file, the write dereferences the attacker-controlled symlink and lands on a path outside the sandbox. The attacker gains write access to files owned by the invoking user.

Successful exploitation requires the victim to install an untrusted opam package, matching the user-interaction requirement in the CVSS vector. The result is a high-integrity impact with no direct confidentiality or availability loss.

Root Cause

The defect is classic symlink following [CWE-61]. opam resolves paths referenced by .install files after symlink resolution rather than before, and it does not verify that resolved targets remain within the sandbox root. This is a time-of-use path validation gap in the .install file handler.

Attack Vector

Exploitation requires an attacker to publish or distribute a crafted opam package and convince a developer or CI system to install it. During installation, the sandboxed build step creates one or more symlinks whose targets fall outside the sandbox directory. The .install phase then writes through those symlinks, placing attacker-controlled content at chosen locations on the host filesystem.

The vulnerability manifests in opam's .install file processing path. Consult the OPAM Release Notes and OSV Vulnerability OSEC-2026-10 for the upstream fix and technical detail.

Detection Methods for CVE-2026-57825

Indicators of Compromise

Unexpected file writes outside the opam sandbox root during opam install operations
Presence of symbolic links inside package build directories that resolve to paths outside the sandbox
Modification of user configuration files, shell profiles, or SSH keys immediately following an opam package installation
Installation of opam packages sourced from untrusted or unverified repositories

Detection Strategies

Inventory opam installations across build hosts and developer workstations, flagging versions before 2.5.2
Enable filesystem auditing on paths outside the opam sandbox root during install operations using auditd or equivalent Linux audit tooling
Review CI/CD pipeline logs for opam invocations that install third-party packages without pinning to trusted revisions
Compare installed opam package hashes against known-good sources to identify tampered artifacts

Monitoring Recommendations

Monitor process creation events for opam invocations followed by writes to sensitive paths such as ~/.ssh, ~/.bashrc, and system configuration directories
Alert on symlink creation inside opam build directories where link targets escape the sandbox root
Track opam package installations from non-default repositories and require review before execution in shared build environments

How to Mitigate CVE-2026-57825

Immediate Actions Required

Upgrade opam to version 2.5.2 or later on all developer workstations, build servers, and CI runners
Apply distribution updates on Debian LTS systems per the Debian LTS Announcement
Restrict opam package sources to trusted repositories and pin package revisions in project manifests
Audit recent installations of untrusted opam packages for unexpected filesystem changes

Patch Information

The opam maintainers fixed this issue in version 2.5.2. Release details are published at the GitHub OPAM Release Notes. Debian LTS users should install the packaged update referenced in the Debian LTS Announcement.

Workarounds

Install opam packages only from vetted internal mirrors until upgrades complete
Run opam install operations as an unprivileged user inside an ephemeral container to constrain the blast radius of a sandbox escape
Disable automatic installation of opam dependencies in CI pipelines and require manual review of package definitions

bash

# Verify the installed opam version and upgrade if below 2.5.2
opam --version

# Debian/Ubuntu: apply distribution security updates
sudo apt update && sudo apt install --only-upgrade opam

# Optional: run opam inside a disposable container to contain sandbox escapes
docker run --rm -it -v "$PWD":/src -w /src ocaml/opam:latest \
  opam install ./my-project.opam