CVE-2026-105280
- Source
- https://cve.org/CVERecord?id=CVE-2026-105280
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-105280.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-105280
- Aliases
-
- EEF-CVE-2026-105280
- GHSA-98jr-23pm-vj7c
- Published
- 2026-10-12T15:30:14Z
- Modified
- 2026-10-13T02:45:32Z
- Severity
-
- 6.9 (Medium) CVSS_V4 - 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 CVSS Calculator
- Summary
- Hex writes unverified package tarballs to standard output in mix hex.package fetch
- Details
-
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.
Hex 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.
Hex 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.
This issue affects hex: from 0.20.2 before 2.5.2.
- Database specific
{ "cna_assigner": "EEF", "cwe_ids": [ "CWE-354" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/105xxx/CVE-2026-105280.json", "unresolved_ranges": [ { "extracted_events": [ { "introduced": "0.20.2" }, { "fixed": "2.5.2" } ], "source": "AFFECTED_FIELD" } ] }- References
-
- https://cna.erlef.org/cves/CVE-2026-105280.html
- https://github.com
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/105xxx/CVE-2026-105280.json
- https://github.com/hexpm/hex
- https://github.com/hexpm/hex/commit/69489f8b74213f03db10169e6e5407e6d5fee512
- https://github.com/hexpm/hex/commit/8a14632ca6ba8a8afd2a3f2098bc267c13e13d93
- https://github.com/hexpm/hex/commit/d1f5a085d9d4748e1f7d195e4bc39ebd77c28d9c
- https://github.com/hexpm/hex/security/advisories/GHSA-98jr-23pm-vj7c
- https://nvd.nist.gov/vuln/detail/CVE-2026-105280
- https://osv.dev/vulnerability/EEF-CVE-2026-105280