{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105280 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-105280 is a medium-severity vulnerability in hexpm hex, published on 12 Oct 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-105280 and fix it if it is affected.\n\nWhat it is: CVE-2026-105280 is a medium-severity vulnerability in hexpm hex, published on 12 Oct 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: There is no known exploitation of CVE-2026-105280 in the wild and no public exploit code.\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-105280/ (Markdown: https://insights.sbomify.com/CVE-2026-105280/index.md)","id":"CVE-2026-105280","markdown":"https://insights.sbomify.com/CVE-2026-105280/index.md","name":"CVE-2026-105280","record":{"aliases":["DEBIAN-CVE-2026-105280","EEF-CVE-2026-105280","GHSA-98jr-23pm-vj7c","UBUNTU-CVE-2026-105280"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Elixir package manager","requires_auth":"none","summary":"A malicious mirror can inject unverified tarballs into stdout during package fetch, potentially leading to code execution or data modification in pipelines.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"Improper Validation of Integrity Check Value vulnerability in hexpm hex allows a package mirror to substitute the tarball that mix hex.package fetch PACKAGE VERSION --output - writes to standard output.\n\nHex compares a fetched tarball's inner and outer checksums with the repository's signed registry before writing it to a file or unpacking it. The standard output branch of mix hex.package fetch writes the bytes returned by Hex.SCM.fetch/3 without that comparison, and Hex.SCM.fetch/3 doesn't verify freshly downloaded tarballs itself. When a mirror configured with HEX_MIRROR_URL or mirror_url serves altered bytes, the command prints them and exits successfully, while the same fetch with --output FILE fails with a checksum mismatch.\n\nHex also prints diagnostics to standard output while the command runs: the body of a failed HTTP response from the update check or a registry fetch, and API warnings from the x-hex-message header. A mirror that answers one of those requests with an error whose body is a tar archive gets that archive written to standard output ahead of the verified tarball, so a pipeline that unpacks standard output extracts the mirror's files. This happens even when the checksum check then fails, because the archive is already on standard output.\n\nThis issue affects hex: from 0.20.2 before 2.5.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Hex writes unverified package tarballs to standard output in mix hex.package fetch","id":"CVE-2026-105280","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Grid Protection Alliance openPDC and openHistorian Missing Authentication for Critical Function","id":"CVE-2026-105281"},"packages":[],"prev":{"headline":"J4Care dcm4che Missing Authentication for Critical Function","id":"CVE-2026-105279"},"products":["hex"],"published":"2026-10-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["hexpm"]},"summary":"A malicious mirror can inject unverified tarballs into stdout during package fetch, potentially leading to code execution or data modification in pipelines.","url":"https://insights.sbomify.com/CVE-2026-105280/"}