Description
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.
Affected products
hex: hex
References6
- github.com/hexpm/hex/security/advisories/GHSA-hmv9-4mfr-m92v ExploitPatchVendor Advisory
- github.com/hexpm/hex/security/advisories/GHSA-hmv9-4mfr-m92v ExploitPatchVendor Advisory
- github.com/hexpm/hex/commit/d7528c8199a1144511508bf3a6460026a5a… Patch
- osv.dev/vulnerability/EEF-CVE-2026-32148 ExploitThird Party Advisory
- cna.erlef.org/cves/CVE-2026-32148.html Third Party Advisory
- github.com/hexpm/hex/commit/e01576f28c64af9fae6eb17e2dad30f6efc…
Metrics
- CVSS 3.1
-
5.9
MEDIUM
Score source: NVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - CVSS 4.0
-
8.9
HIGH
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 0% percentile: 9 · as of 13 November 2026
- CWE
- CWE-354CWE-494
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.