CVE-2026-32148
Dependency integrity bypass in Hex.RemoteConverger allows tampered dependencies to pass.
Is CVE-2026-32148 being exploited?
Not confirmed. CVE-2026-32148 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.19% probability of exploitation in the next 30 days.
How severe is CVE-2026-32148?
CVE-2026-32148 is rated High with a CVSS score of 8.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-32148?
Yes. A fix has been recorded for CVE-2026-32148. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32148 affect?
CVE-2026-32148 affects Hex, Hex.RemoteConverger, mix.lock. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32148?
Upgrade Hex to 2.4.2+; refresh lockfiles; audit caches.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers with cached registry access can inject modified dependencies; mix.lock is rewritten with registry checksums, masking tampering.
Patch when possible
- affected>= 0.16.0 and < 2.4.2
- affected>= e01576f28c64af9fae6eb17e2dad30f6efcb303c and < d7528c8199a1144511508bf3a6460026a5a14c8e
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.