Answer in brief
CVE-2026-105274 records a Low severity (CVSS 2.1) vulnerability in hex_core decompresses registry and Erlang term API responses without size limits. The current sources do not mark it as known exploited. The current feed maps erlang/erlang/rebar3 (generic), hexpm/hex (generic), hexpm/hex_core (generic), hexpm/hexpm/hex (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 2.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps erlang/erlang/rebar3 (generic), hexpm/hex (generic), hexpm/hex_core (generic), hexpm/hexpm/hex (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| erlang/erlang/rebar3generic | >=209c02ec57c2cc3207ee0174c3af3675b8dc8f79 <* | * |
| hexpm/hexgeneric | >=2.1.0 <2.5.2 | 2.5.2 |
| hexpm/hex_coregeneric | >=0.1.0 <0.20.0 | 0.20.0 |
| hexpm/hexpm/hexgeneric | >=671f695ac548ed01f5828c2a739ecaa942b21007 <d8b60eee97abb119d525306f048969a217d793a5 | d8b60eee97abb119d525306f048969a217d793a5 |
| hexpm/hexpm/hex_coregeneric | >=fbb6d9de472e5edb8d6fb6b32a91cb266137892e <ebe25d110717f6a3addba5232cd4a7dc1c76b628 | ebe25d110717f6a3addba5232cd4a7dc1c76b628 |
| erlang/rebar3generic | >=3.9.1 <* | * |
Published upstream
Oct 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 12, 2026
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 onward; hex: from 2.1.0 before 2.5.2; hex_core: from 0.1.0 before 0.20.0.
Quoted source text, attributed separately from HOL analysis.