8.9
/ 10
HIGH
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
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.
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.
AI Analysis
Insufficient Verification of Data Authenticity vulnerability in hexpm hex allows dependency integrity bypass via unverified lockfile checksums
Basic Information
ID
CVE-2026-32148
Source
EEF
Published
Apr 30, 2026 at 18:17
Modified
Apr 30, 2026 at 19:03
Affected Product
Vendor
hexpm
Product
hex
Version
0.16.0
Affected Versions
hexpm hex 0.16.0
hexpm hex e01576f28c64af9fae6eb17e2dad30f6efcb303c
hexpm hex e01576f28c64af9fae6eb17e2dad30f6efcb303c
CWE Classification
AI Assessment
AI Score
8.9 / 10
AI Severity
High
Vendor
hexpm
Product
hex
Version
0.16.0-2.4.2