CVE-2026-32148
HIGHDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 9% of all known CVEs.
References
Related Vulnerabilities
Other CWE-354 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-48795 | Medium | 5.9 | 93% | - | Fix |
| CVE-2019-1166 | Medium | 5.9 | 68% | - | - |
| CVE-2024-3596 | Critical | 9.0 | 15% | - | Fix |
| CVE-2020-26141 | Medium | 6.5 | 3.1% | - | Fix |
| CVE-2020-25862 | High | 7.5 | 2.4% | - | Fix |
| CVE-2023-38802 | High | 7.5 | 1.8% | - | Fix |
Common questions
How do I fix CVE-2026-32148?
Upgrade hex to 2.4.2 or later.
Is CVE-2026-32148 being actively exploited?
Not that we know of. CVE-2026-32148 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.19% is the estimated probability that it will be exploited in the next 30 days. That is higher than 9% of all scored CVEs.
How severe is CVE-2026-32148?
CVE-2026-32148 has a CVSS v3 base score of 5.9, rated important. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-32148 affect?
Published advisories record a fix for hex (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-32148
Markdown
[](https://tridentstack.com/cve/CVE-2026-32148)HTML
<a href="https://tridentstack.com/cve/CVE-2026-32148"><img src="https://tridentstack.com/cve/badge/CVE-2026-32148.svg" alt="CVE-2026-32148"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-05.