Skip to content
statance
MenuClose
medium · CVSS 5.9

CVE-2026-96596

erl_tar:extract/2 loops forever on a GNU sparse member with a trailing hole

Published 14 Oct 2026 · Source updated 19 Nov 2026 · Retrieved 2026-11-19 08:29 UTC

Statance checks for CVE-2026-96596. Connected servers are checked automatically against the fixed versions their distribution or package ecosystem has published for it, including app dependency lockfiles. Check my servers ↗
Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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 stdlib from 8.0 before 8.1.1, and rebar3 from 3.27.1 before 3.28.0, and hex from 2.4.2 before 2.5.3; hex_core: from 0.14.0 before 0.20.1.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
otpErlangaffected: 29.0 to < 29.1.2See vendor advisory
stdlibErlangaffected: 8.0 to < 8.1.1See vendor advisory
erlang/otpErlangaffected: fbf2c7194f6fce4b7b66dc0bcaa4f6b4b85e088f to < 3086307f311b78b38644a7787a3aca6a3f95a9d5See vendor advisory
rebar3erlangaffected: 3.27.1 to < 3.28.0See vendor advisory
erlang/rebar3erlangaffected: 23dbdb5d1f87f56902aef296c88a20049cd0c6e4 to < 310e2ec8c7dd3df05d67af2b7fae23f30fc523c4See vendor advisory
hex_corehexpmaffected: 0.14.0 to < 0.20.1See vendor advisory
hexpm/hex_corehexpmaffected: 13bb9fbba418a406af614790b8d5cd458259ee70 to < a2ece683e6e88a3ec95ad20b09aca426e08b372eSee vendor advisory
hexhexpmaffected: 2.4.2 to < 2.5.3See vendor advisory
hexpm/hexhexpmaffected: 5543a1919c709d8eb2b317f62aad76ca1eed375c to < * (version-specific exceptions; see source)See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed