CVE-2026-105274
Low 2.1No known exploitationFix availablehex_core decompresses registry and Erlang term API responses without size limits
Record last updated
CVSS score
Low on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 40% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Weakness: CWE-409
Patching and mitigation
- Patch status
- Fix available (source: CVE record (EEF))
- Fix documented (source date)
- Vendor solution
- 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.
- Mitigation
- Point repository URLs at repo.hex.pm or a mirror you operate, and the API URL at hex.pm. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| erlang | rebar3 | from 209c02ec57c2cc3207ee0174c3af3675b8dc8f79 before 360838a22f5b3a88c0358207f2923059bcbb3afb | 360838a22f5b3a88c0358207f2923059bcbb3afb | CVE Program |
| erlang | rebar3 | from 3.9.1 before 3.27.3 | 3.27.3 | CVE Program |
| hexpm | hex | from 2.1.0 before 2.5.2 | 2.5.2 | CVE Program |
| hexpm | hex | from 671f695ac548ed01f5828c2a739ecaa942b21007 before d8b60eee97abb119d525306f048969a217d793a5 | d8b60eee97abb119d525306f048969a217d793a5 | CVE Program |
| hexpm | hex | 2.6.0 | Not documented | CVE Program |
| hexpm | hex_core | from 0.1.0 before 0.20.0 | 0.20.0 | CVE Program |
| hexpm | hex_core | from fbb6d9de472e5edb8d6fb6b32a91cb266137892e before ebe25d110717f6a3addba5232cd4a7dc1c76b628 | ebe25d110717f6a3addba5232cd4a7dc1c76b628 | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (EEF)
Vendor guidance and references
- Fix commit 360838a in erlang/rebar3 (opens in a new tab)patch
- Fix commit d8b60ee in hexpm/hex (opens in a new tab)patch
- Fix commit ebe25d1 in hexpm/hex_core (opens in a new tab)patch
- GitHub Advisory (opens in a new tab)related, vendor-advisory
- EEF CNA record for CVE-2026-105274 (opens in a new tab)related
- Introducing commit 209c02e in erlang/rebar3 (opens in a new tab)related
- Introducing commit 671f695 in hexpm/hex (opens in a new tab)related
- Introducing commit fbb6d9d in hexpm/hex_core (opens in a new tab)related
- OSV record EEF-CVE-2026-105274 (opens in a new tab)related