CVE-2026-105280
Last modified
CVE-2026-105280 is a medium-severity vulnerability rated 6.9/10 on the CVSS scale. 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. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
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. 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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| hexpm | hex | >= 0.20.2, < 2.5.2 |
| hexpm | hex | >= d1f5a085d9d4748e1f7d195e4bc39ebd77c28d9c, < * |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-105280?
How severe is CVE-2026-105280?
How do I fix CVE-2026-105280?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-105273MP4Parser does not adequately validate MP4 box sizes. A malf…7.5
- CVE-2026-105274Improper Handling of Highly Compressed Data (Data Amplificat…2.1
- CVE-2026-105275Satel Netco Design versions prior to v2.1.7 contains a relat…4.3
- CVE-2026-105278The published Docker image for openPDC includes a fixed admi…9.8
- CVE-2026-105279In the default configuration, the archive accepts DICOM asso…9.1
- CVE-2026-10528A security flaw has been discovered in Orthanc DICOM Server …3.3
- CVE-2026-105281The internal data publisher on openPDC accepts network conne…7.5
- CVE-2026-105283Generation of Error Message Containing Sensitive Information…6.3
- CVE-2026-105284A weakness has been identified in Totolink A3002MU 1.0.0-B20…10
- CVE-2026-105285A security vulnerability has been detected in Totolink A3002…10
- CVE-2026-105286A vulnerability was detected in Totolink A3002MU 1.0.0-B2023…6.3
- CVE-2026-105287A flaw has been found in feelec-yishu feelcrm-os 1.0.0. Affe…6.3
Are you affected by CVE-2026-105280?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
