cve.bz

CVE-2026-105274 hex_core decompresses registry and Erlang term API responses without size limits

2.1 lowEPSS 0.4%Fix available

Low (2.1). EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in hex_core 0.20.0.

On this page
Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in hexpm hex_core allows an untrusted repository mirror, or a server answering hex_core's API requests, to exhaust the memory of the Erlang VM running hex_core. The same code is vendored in Hex (mix_hex_repo, mix_hex_api) and rebar3 (r3_hex_repo, r3_hex_api). hex_repo:get_names/1, hex_repo:get_versions/1, hex_repo:get_package/2 and hex_repo:get_policy/2 decompress the registry response with zlib:gunzip/1 and decode the signed envelope before verifying its signature. A mirror doesn't have the repository's private key, but it chooses the compressed bytes, so a small response decompresses into an envelope of any size before the signature check rejects it. hex_api decodes responses with the application/vnd.hex+erlang content type through hex_safe_binary_to_term:safe_binary_to_term/1, which calls binary_to_term(Binary, [safe]). The safe option prevents atom creation, but it accepts compressed terms and doesn't limit the size of the decoded term, and the check that rejects functions and ports runs after the term has been built. The fix for CVE-2026-21619 added the safe option and that check without bounding the decoded size. This issue affects rebar3: from 3.9.1 before 3.27.3; hex: from 2.1.0 before 2.5.2 and from 2.6.0 onward; hex_core: from 0.1.0 before 0.20.0.

Severity

CVSS 4.0

2.1 low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th 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-15. 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-409 Improper Handling of Highly Compressed Data (Data Amplification)
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-105274 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105274?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105274?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-105274 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 hex_corefrom 0.1.0 before 0.20.0
erlang rebar3from 3.9.1 before 3.27.3
hexpm hexfrom 2.1.0 before 2.5.2
hexpm hex2.6.0 and later

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-105274Hexhex_core>=0.1.0 <0.20.00.20.0
EEF-CVE-2026-105274no fix published
EEF-CVE-2026-1052743.27.1, 3.27.0, 3.26.0, 3.25.1, 3.25.0 and 24 moreno fix published
EEF-CVE-2026-105274v2.5.1, v2.5.0, v2.2.2, v2.4.2, v2.4.1 and 5 moreno fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13rebar3no fix listedDEBIAN-CVE-2026-105274
Debian14erlang-hex2.5.3-2DEBIAN-CVE-2026-105274
Debian14rebar33.27.3-1DEBIAN-CVE-2026-105274
Ubuntu22.04:LTSrebar3no fix listedUBUNTU-CVE-2026-105274
Ubuntu24.04:LTS, 26.04:LTS, 26.10rebar3, erlang-hexno fix listedUBUNTU-CVE-2026-105274

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 Low.

Red Hat's statement

This vulnerability is rated as Low impact because exploitation requires control of a repository mirror or man-in-the-middle network position, and the affected components run within transient build tools rather than persistent production services. Memory exhaustion crashes the Erlang VM running the build, but recovery requires only restarting the process against a trusted mirror. Red Hat Enterprise Linux does not ship hex_core or rebar3 in supported product channels; exposure is limited to Fedora community packages in developer environments.

Red Hat's mitigation

Configure build tools to fetch packages only from trusted, official registry endpoints. Avoid configuring untrusted third-party repository mirrors.

Ensure the HEX_MIRROR_URL environment variable is unset or points to a trusted, internal mirror over verified HTTPS. Note that HTTPS protects against man-in-the-middle injection but does not protect against a compromised mirror serving malicious responses directly.

Environments that depend on third-party mirrors cannot fully mitigate this vulnerability if those mirrors are untrusted, as any mirror can craft compressed responses that trigger memory exhaustion during dependency resolution.

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-105274.

References

Check your stackJSON