cve.bz

CVE-2026-105280 Hex writes unverified package tarballs to standard output in mix hex.package fetch

6.9 mediumEPSS 0.2%

Medium (6.9) in hexpm hex. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

6.9 medium
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
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-354 Improper Validation of Integrity Check Value
Published
Modified
Assigned by
EEF (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105280 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105280?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105280?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105280 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
hexpm hexfrom 0.20.2 before 2.5.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13erlang-hexno fix listedDEBIAN-CVE-2026-105280
Debian14erlang-hex2.5.3-2DEBIAN-CVE-2026-105280
Ubuntu24.04:LTS, 26.04:LTS, 26.10erlang-hexno fix listedUBUNTU-CVE-2026-105280

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate severity vulnerability was found in hex, the package manager for the Erlang/Elixir ecosystem. When 'mix hex.package fetch PACKAGE VERSION --output -' streams a package to standard output, hex writes the bytes returned by Hex.SCM.fetch/3 without comparing the tarball's inner and outer checksums against the repository's signed registry, a verification that is performed when output is written to a file. A malicious or compromised package mirror configured through HEX_MIRROR_URL or mirror_url can therefore substitute the tarball written to standard output; in addition, diagnostics that hex prints to standard output (bodies of failed HTTP responses and API warnings) can deliver an attacker-controlled archive ahead of the verified tarball. Build pipelines that unpack standard output can consequently extract substituted files without detecting tampering, which can lead to arbitrary code execution. Red Hat rates this flaw moderate severity with a CVSS 3.1 base score of 5.3 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N), lower than the upstream CVSS 4.0 score of 6.9, mainly because exploitation requires the non-default combination of a configured mirror and standard-output fetching. Within Red Hat's product scope this issue affects the community rust-hex component in Fedora and EPEL; resolution is delegated and a fix is being pursued through the community process.

Red Hat's mitigation

Avoid streaming fetched packages directly to standard output. Run 'mix hex.package fetch PACKAGE VERSION --output FILE' instead of '--output -' so that hex verifies the tarball's inner and outer checksums against the signed registry; a fetch of altered bytes to a file fails with a checksum mismatch. Configure only trusted mirrors (HEX_MIRROR_URL or mirror_url), and do not pipe or unpack unverified standard output in automated build pipelines. The upstream fix is available in hex 2.5.2; updating to a version containing this fix is recommended when it becomes available through your distribution.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105280.

Attack patterns (CAPEC)

  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-145 Checksum Spoofing Severity: Medium
  • CAPEC-463 Padding Oracle Crypto Attack Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON