CVE-2026-105274
hex_core decompresses registry and Erlang term API responses without size limits
- Low 2.1
Description
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.
Key facts
- Published
- 12 Oct 2026
- Last changed
- 11 Nov 2026
- Assigned by
- EEF
- EPSS
- 0.447% likely to be exploited in the next 30 days, higher than 39.544% of CVEs (scores for 18 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 2.1CVSS 4.0, Lowfrom the CNA (EEF)
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
What to do
- Upgrade hex_core to 0.20.0 or later. Registry resources larger than 16 MiB after decompression are rejected with {too_big_uncompressed, MaxSize}, configurable with registry_max_uncompressed_size. Upgrade Hex to 2.5.2 or later, which vendors hex_core 0.20.0. No rebar3 release vendors hex_core 0.20.0 yet.CNA solution statement
- Point repository URLs at repo.hex.pm or a mirror you operate, and the API URL at hex.pm.CNA workaround statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
A mirror can make every registry fetch allocate memory far beyond the size of its response: in a test against Hex main 851b938, which vendors this code, a 65 KB registry response decompressed into a 64 MiB envelope before the signature check failed. The API server, or an attacker who can alter its responses, can do the same with API responses: 8 KB of compressed Erlang term format decoded into a list of 4.2 million elements. Large enough responses stop the Erlang VM, which fails the build tool command or the program using hex_core. No package code has to run. (CNA impact statement)
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| hexpm | hex_core |
|
| hexpm | hex_core |
|
| erlang | rebar3 |
|
| erlang | rebar3 |
|
| hexpm | hex |
|
| hexpm | hex |
|
Timeline
- 12 Oct 2026 Published
Weakness
References
- GitHub Advisory
- EEF CNA record for CVE-2026-105274
- OSV record EEF-CVE-2026-105274
- Introducing commit fbb6d9d in hexpm/hex_core
- Fix commit ebe25d1 in hexpm/hex_core
- Introducing commit 209c02e in erlang/rebar3
- Fix commit 360838a in erlang/rebar3
- Introducing commit 671f695 in hexpm/hex
- Fix commit d8b60ee in hexpm/hex