PoC Monitor
← All CVEs
CVE-2026-96612published 12 Oct 2026 15:39 UTCData: JSON · API

Hex

Path traversal in Hex via unvalidated dependency app names

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA · CWE-22
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

hexpm hex
  • >= 0.6.0, < 2.5.2

Fixed in 2.5.2

hexpm hex
  • >= 380f87054e1bc08ee13d2b5311bc01f98dad2fc6, < *

Fixed in *, 1b3e2ae8f0dd7273a2c2625b9e50b6c67c8568fb, 72279a8e2004b32b20d8767ff010c117193dd02c

Mitigation

Upgrade Hex to 2.5.2 or later, for example with mix local.hex. Hex then skips package releases that give a dependency an application name other than a letter followed by letters, digits, _ and -, and warns about them. Resolution fails if no other release of the package fits the requirements.

Workaround

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

References

1 more

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published12 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.