CVE Catalog

CVE-2026-32148

MediumCVSS 5.9
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.19%

9th percentile - higher than 9% of all known CVEs

Summary

In the Hex.RemoteConverger module of the hexpm hex library, dependency checksum verification is silently skipped due to a type mismatch (string-based vs. atom-based names), causing the verification code path to be bypassed. This allows dependency integrity bypass when an attacker can influence cached packages or the registry, and mix.lock is silently rewritten with registry checksums, erasing evidence of tampering. Affects hex from 0.16.0 before 2.4.2.

Risk Assessment

Modified dependencies may be accepted without detection, enabling injection of malicious code into the build process and application, while mix.lock overwriting hinders detection of the compromise.

Recommendation

Upgrade the hex library to version 2.4.2 or later. Additionally, secure the package cache and registry and monitor for unexpected changes to mix.lock.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS