Skip to content
Threat Brief

← All advisories

CVE-2026-105274

Low 2.1No known exploitationFix available

hex_core decompresses registry and Erlang term API responses without size limits

Record last updated

CVSS score

2.1

Low on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 40% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

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

VendorProductAffected versionsFixed inPer
erlangrebar3from 209c02ec57c2cc3207ee0174c3af3675b8dc8f79 before 360838a22f5b3a88c0358207f2923059bcbb3afb360838a22f5b3a88c0358207f2923059bcbb3afbCVE Program
erlangrebar3from 3.9.1 before 3.27.33.27.3CVE Program
hexpmhexfrom 2.1.0 before 2.5.22.5.2CVE Program
hexpmhexfrom 671f695ac548ed01f5828c2a739ecaa942b21007 before d8b60eee97abb119d525306f048969a217d793a5d8b60eee97abb119d525306f048969a217d793a5CVE Program
hexpmhex2.6.0Not documentedCVE Program
hexpmhex_corefrom 0.1.0 before 0.20.00.20.0CVE Program
hexpmhex_corefrom fbb6d9de472e5edb8d6fb6b32a91cb266137892e before ebe25d110717f6a3addba5232cd4a7dc1c76b628ebe25d110717f6a3addba5232cd4a7dc1c76b628CVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references