# CVE-2026-32148: Insufficient Verification of Data Authenticity vulnerability in hexpm hex (Hex.RemoteConverger module) allows…

Source: https://junglewise.ai/threats/cve-2026-32148-insufficient-verification-of-data-authenticity-vulnerability-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-30  
License: CC BY 4.0 with a link back

CVE-2026-32148 · Severity: medium · CVSS 5.9 · Published 2026-04-30

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.

Technologies: [Hex (Hex)](https://junglewise.ai/threats/technologies/hex). Vendors: [Hex](https://junglewise.ai/threats/vendors/hex).

## Quick answers

**Is CVE-2026-32148 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-32148 being exploited in the wild.

**How severe is CVE-2026-32148?** Medium severity, with a CVSS score of 5.9, published 30 April 2026.

**Which products and versions are affected?** Hex (Hex). The advisory does not name versions.

**Is there a fix for CVE-2026-32148?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**Am I affected by CVE-2026-32148?** Check whether you run Hex (Hex). Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Affected products

- Hex (Hex)

## Related threats

- [hexpm hexpm Cross-Site Scripting in OAuth Authorization View](https://junglewise.ai/threats/cve-2026-21618-hexpm-hexpm-cross-site-scripting-in-oauth-authorization-view)