Not a U.S. government website. NDD is an independent vulnerability database by Volerion and is not affiliated with or endorsed by NIST or NVD.
VOLERION
Volerion Security Research

NOT DEFERRED DATABASE

VULNERABILITIES

CVE-2026-96612 Details

ANALYZED


This CVE record has been analyzed and enriched by NVDAPI.com as an independent party.

Description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in hexpm hex allows a malicious package publisher to delete a directory outside the project's deps directory and extract package files into it when a developer fetches dependencies. A package release's requirements carry an app label that names the dependency's OTP application. Hex takes this label from the repository's signed registry and uses it as the dependency's application name without validating it (Hex.RemoteConverger.deps/2, Hex.Mix.to_lock/1). Mix derives the dependency's checkout directory as deps/<app>, and Hex.SCM.update/1 runs File.rm_rf!/1 on that directory and unpacks the package into it. hex.pm only checks the label's length, so a publisher can set it to a value such as ../../target. When a project depends on such a release directly or transitively, mix deps.get or mix deps.update deletes the directory the label resolves to and writes the labelled package's files there. This happens before any dependency code is compiled. This issue affects hex: from 0.6.0 before 2.5.2.

Metrics

CVSS 3.x Severity and Vector Strings:

References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.

Weakness Enumeration

CWE-IDCWE NameSource
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')EEF

Affected Products

ProductVersions
hexpm hex
>= 0.6.0, < 2.5.2 (semver)

CPE

  • No CPEs found in CPE dictionary for this product.

Remediation

  • Upgrade: 2.5.2moderate effort
  • Workaround:low effort

    Before running `mix deps.get` on a `mix.lock` from an untrusted change, verify that every key in `mix.lock` is a plain application name without `/`, `\` or `..`. There is no workaround for new dependency resolution with `mix deps.update` or `mix deps.get` without a lock entry.

Change History

2 change records found show changes


QUICK INFO

CVE Dictionary Entry:
CVE-2026-96612
NVD Published Date:
Oct 12, 2026
NVD Last Modified:
Oct 16, 2026
Source:
EEF
CVE-2026-96612 Details - Not Deferred