CVE-2026-32148Lockfile checksums not verified in Hex allows dependency integrity bypass

Official 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 packages & fixed versions

Affected products (as reported)

References

• https://github.com/hexpm/hex/security/advisories/GHSA-hmv9-4mfr-m92v vendor-advisory, related
• https://cna.erlef.org/cves/CVE-2026-32148.html related
• https://osv.dev/vulnerability/EEF-CVE-2026-32148 related
• https://github.com/hexpm/hex/commit/d7528c8199a1144511508bf3a6460026a5a14c8e patch