{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32148 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-32148 is a high-severity vulnerability in hexpm hex, published on 30 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-32148 and fix it if it is affected.\n\nWhat it is: CVE-2026-32148 is a high-severity vulnerability in hexpm hex, published on 30 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32148 exists.\n\nAffected product: hexpm hex. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32148/ (Markdown: https://insights.sbomify.com/CVE-2026-32148/index.md)","id":"CVE-2026-32148","markdown":"https://insights.sbomify.com/CVE-2026-32148/index.md","name":"CVE-2026-32148","record":{"aliases":["DEBIAN-CVE-2026-32148","EEF-CVE-2026-32148","GHSA-hmv9-4mfr-m92v","UBUNTU-CVE-2026-32148"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir package manager","requires_auth":"none","summary":"Attackers can bypass dependency integrity checks in Hex by exploiting a type mismatch, allowing malicious code execution via tampered packages.","user_interaction":"required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[{"product":"hex","vendor":"hex"}],"cvss":{"score":8.9,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-494","name":"Download of Code Without Integrity Check"},{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"Insufficient Verification of Data Authenticity vulnerability in hexpm hex (Hex.RemoteConverger module) allows dependency integrity bypass via unverified lockfile checksums.\n\nHex 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.\n\nAn 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.\n\nThis issue affects hex: from 0.16.0 before 2.4.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Lockfile checksums not verified in Hex allows dependency integrity bypass","id":"CVE-2026-32148","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Windows Hyper-V Remote Code Execution Vulnerability","id":"CVE-2026-32149"},"packages":[],"prev":{"headline":"SFTP chroot bypass via path traversal in SSH_FXP_FSETSTAT","id":"CVE-2026-32147"},"products":["hex"],"published":"2026-04-30","related":[{"cvss_score":8.8,"headline":"Supply chain in n/a","id":"CVE-2019-1000012","kev_date_added":null,"published":"2019-02-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-01","vendors":["hexpm"]},"summary":"Attackers can bypass dependency integrity checks in Hex by exploiting a type mismatch, allowing malicious code execution via tampered packages.","url":"https://insights.sbomify.com/CVE-2026-32148/"}