Description
Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in benoitc hackney allows Excessive Allocation. The Alt-Svc response header parser in src/hackney_altsvc.erl does not guarantee forward progress. When parse_token/2 receives a non-token, non-whitespace, non-comma byte (e.g. !, @, =, ;), it returns the input unchanged. skip_comma/1 also returns the buffer unchanged when the first byte is not a comma. parse_entries/2 then recurses with identical data, creating a tight infinite tail-recursive loop that pins a scheduler at 100% CPU. The calling process never returns. The entry point parse_and_cache/3 is called synchronously in the connection process on every HTTP response. A single-byte Alt-Svc: ! response header is sufficient to trigger the hang; the header is fully controlled by any HTTP origin the client connects to. This issue affects hackney: from 2.0.0-beta.1 before 4.0.1.
Problem types
CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
Product status
2.0.0-beta.1 (semver) before 4.0.1
408e5fe20302226ea8c74dde2bcbd452d712b5b2 (git) before e548aba1f97ffa3f4750da7b772998fb78c01894
Credits
Peter Ullrich
Benoit Chesneau
Jonatan Männchen / EEF
References
github.com/...ackney/security/advisories/GHSA-6cp8-v795-jr2j
github.com/...ackney/security/advisories/GHSA-6cp8-v795-jr2j
cna.erlef.org/cves/CVE-2026-47066.html
osv.dev/vulnerability/EEF-CVE-2026-47066
github.com/...ommit/e548aba1f97ffa3f4750da7b772998fb78c01894