Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.9
CVE-2026-32148: Hex allows altered dependencies without checksum check
CVE-2026-32148 · published 5 months ago
Summary
The Hex package manager does not verify the checksums recorded in its lock file, so changes to dependency code can go unnoticed. An attacker who can modify the package cache or registry could insert malicious code that will be accepted during builds. Upgrade Hex to version 2.4.2 or later to restore proper checksum verification.
What to do
- Update debian erlang-hex to version 2.4.2-2.
- Update hex hex to version 2.4.2 or later.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | hex | hex |
>= 0.16.0, < 2.4.2 cpe:2.3:a:hex:hex:*:*:*:*:*:*:*:* |
| Debian:13 | debian | erlang-hex | All versions |
| Debian:14 | debian | erlang-hex |
< 2.4.2-2 Fix: upgrade to 2.4.2-2
|
| Ubuntu:24.04:LTS | canonical | erlang-hex | All versions |
Original advisory text
Lockfile checksums not verified in Hex allows dependency integrity bypass
Insufficient Verification of Data Authenticity vulnerability in hexpm hex (Hex.RemoteConverger module) allows dependency integrity bypass via unverified lockfile checksums.
Hex stores checksums for dependencies in the mix.lock file to ensure reproducible and integrity-checked builds. However, Hex.RemoteConverger.verify_resolved/2 never executes checksum verification because the lock data returned by Hex.Utils.lock/1 uses string-based dependency names, while the verification logic compares against atom-based names. This type mismatch causes the verification code path to be silently skipped. Checksums are still validated when packages are initially downloaded from the registry, but mismatches between the lockfile and resolved dependencies are not detected.
An attacker who can influence cached packages (e.g., via local cache poisoning or a compromised registry) can provide modified dependency contents that will be accepted without detection. The mix.lock file is silently rewritten with the checksum values from the registry, erasing evidence of tampering.
This issue affects hex: from 0.16.0 before 2.4.2.
Hex stores checksums for dependencies in the mix.lock file to ensure reproducible and integrity-checked builds. However, Hex.RemoteConverger.verify_resolved/2 never executes checksum verification because the lock data returned by Hex.Utils.lock/1 uses string-based dependency names, while the verification logic compares against atom-based names. This type mismatch causes the verification code path to be silently skipped. Checksums are still validated when packages are initially downloaded from the registry, but mismatches between the lockfile and resolved dependencies are not detected.
An attacker who can influence cached packages (e.g., via local cache poisoning or a compromised registry) can provide modified dependency contents that will be accepted without detection. The mix.lock file is silently rewritten with the checksum values from the registry, erasing evidence of tampering.
This issue affects hex: from 0.16.0 before 2.4.2.
References
- https://github.com URL
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/32xxx/CVE-2026-32148... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-32148 Vendor Advisory
- https://github.com/hexpm/hex Product
- https://cna.erlef.org/cves/CVE-2026-32148.html URL
- https://osv.dev/vulnerability/EEF-CVE-2026-32148 URL
- https://github.com/hexpm/hex.git Product
- https://github.com/hexpm/hex/commit/d7528c8199a1144511508bf3a6460026a5a14c8e Patch
- https://github.com/hexpm/hex/security/advisories/GHSA-hmv9-4mfr-m92v Vendor Advisory
- https://security-tracker.debian.org/tracker/CVE-2026-32148 Vendor Advisory
- https://ubuntu.com/security/CVE-2026-32148 Third Party Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-32148 Third Party Advisory
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker full control
Type
CWE-354Improper Validation of Integrity Check Value
CWE-494Download of Code Without Integrity Check
Timeline
Published30 Apr 2026
Updated9 Oct 2026
First seen30 Apr 2026
Sources
EEF-CVE-2026-32148 · OSV
CVE-2026-32148 · NVD
GHSA-hmv9-4mfr-m92v · GHSA
DEBIAN-CVE-2026-32148 · OSV
UBUNTU-CVE-2026-32148 · OSV
CVE-2026-32148 · OSV
Track software like this
Free during beta