Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in Erlang OTP stdlib (erl_tar module), hexpm hex_core (hex_erl_tar module), hexpm hex (mix_hex_erl_tar module) and erlang rebar3 (r3_hex_erl_tar module) allows an attacker who supplies a tar archive to cause a denial of service via a crafted GNU sparse member.
When erl_tar:extract/1,2 writes a member to disk, erl_tar:stream_to_file_loop/3 reads it in chunks of 65536 bytes by default. For a GNU sparse member whose sparse map ends before its real size, erl_tar:do_sparse_read/3 matches its trailing-hole clause before its zero-length clause. After the chunk is used up, the trailing-hole clause reads zero bytes, does not advance the position, and recurses forever. A 2048-byte archive keeps the extracting process and one scheduler busy until the process is killed. The {max_size, N} option prevents this only when N is below the real size of the member. Extraction with the memory option is not affected.
hex_core ships its own copy of erl_tar as hex_erl_tar, and Hex and rebar3 ship hex_core with prefixed module names (mix_hex_erl_tar and r3_hex_erl_tar). These copies contain the same code and do not call stdlib's erl_tar, so they are affected on any OTP version. OTP 28 is not affected, but an application running on OTP 28 is affected if it extracts archives through an affected version of hex_core, Hex or rebar3.
This issue affects OTP from OTP 29.0 before OTP 29.1.2, corresponding to rebar3 from 3.27.1 before 3.28.0, and stdlib from 8.0 before 8.1.1, and hex from 2.4.2 before 2.5.3; hex_core: from 0.14.0 before 0.20.1.
CVE-2026-105274 is a low-severity vulnerability in hexpm's hex_core and related tools that allows an untrusted repository mirror or server to exhaust the Erlang VM memory by sending highly compressed data that decompresses to a large size before signature verification. This improper handling of compressed data can lead to resource exhaustion. The issue affects hex_core versions before 0.20.0, rebar3 versions from 3.9.1 before 3.27.3, and hex versions from 2.1.0 before 2.5.2 and from 2.6.0 onward. Fixes have been released in hex_core 0.20.0, rebar3 3.27.3, and hex 2.5.2.
CVE-2026-103502 is an improper certificate validation vulnerability in the hexpm hex_core library affecting versions from 0.1.0 up to but not including 0.20.0. The issue arises because hex_core's default HTTP adapter on Erlang/OTP 24 and OTP 25 (when the OS CA certificates cannot be loaded) does not verify server certificates properly, allowing an attacker who can intercept HTTPS connections to impersonate hex.pm or related repositories. The vulnerability stems from fallback behavior that disables certificate verification without clear documentation or warnings. hex_core 0.11.0 introduced secure SSL defaults for OTP 25+, but earlier versions and certain OTP configurations remain vulnerable. The CVSS 4.0 score is 5.9 (medium severity).
Uncontrolled Resource Consumption, Deserialization of Untrusted Data vulnerability in hexpm hex_core (hex_api modules), hexpm hex (mix_hex_api modules), erlang rebar3 (r3_hex_api modules) allows Object Injection, Excessive Allocation. This vulnerability is associated with program files src/hex_api.erl, src/mix_hex_api.erl, apps/rebar/src/vendored/r3_hex_api.erl and program routines hex_core:request/4, mix_hex_api:request/4, r3_hex_api:request/4.
This issue affects hex_core: from 0.1.0 before 0.12.1; hex: from 2.3.0 before 2.3.2; rebar3: from 3.9.1 before 3.27.0.