CVE-2026-105274: CWE-409 Improper Handling of Highly Compressed Data (Data Amplification) in erlang rebar3
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; hex_core: from 0.1.0 before 0.20.0.
CVSS v4.0
Score 2.1low
Affected software
erlang
rebar3
erlang
rebar3
hexpm
hex_core
hexpm
hex_core
hexpm
hex
hexpm
hex
cpe:2.3:a:erlang:rebar3:*:*:*:*:*:*:*:*cpe:2.3:a:hexpm:hex_core:*:*:*:*:*:*:*:*cpe:2.3:a:hexpm:hex:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-105274) involves improper handling of highly compressed data in the Erlang hexpm hex_core library and related tools (hex and rebar3). The affected functions decompress registry responses using zlib:gunzip/1 and decode signed envelopes before verifying signatures. Because the decompression occurs before signature verification, a malicious mirror can send a small compressed payload that expands into a very large envelope, causing memory exhaustion (data amplification). Additionally, the decoding uses binary_to_term with the safe option, which prevents atom creation but still allows decompression of terms without size limits, enabling large memory consumption before rejecting unsafe terms. The vulnerability affects rebar3 versions >=3.9.1, hex versions >=2.1.0 and <2.5.2, and hex_core versions >=0.1.0 and <0.20.0.
Potential Impact
An attacker controlling an untrusted repository mirror or a server responding to hex_core API requests can cause the Erlang VM running hex_core to exhaust memory by sending a small compressed response that decompresses into a very large data structure. This can lead to denial of service due to resource exhaustion. There is no indication of code execution or data corruption. The impact is limited to resource exhaustion.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official patch links were provided, users should monitor for vendor updates addressing this vulnerability. Until a fix is available, avoid using untrusted repository mirrors or servers for hex_core, hex, and rebar3 API requests to mitigate risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-10-10T13:00:02.355Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6acd13082cdf04f656b5556a
Added to database: 10/12/2026, 17:04:08 UTC
Last enriched: 10/12/2026, 17:18:46 UTC
Last updated: 10/12/2026, 19:04:04 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.