Description
Loop with Unreachable Exit Condition (‘Infinite Loop’) vulnerability in mtrudel bandit allows unauthenticated remote denial of service via worker process exhaustion. ‘Elixir.Bandit.HTTP1.Socket’:do_read_chunked_data!/5 in lib/bandit/http1/socket.ex terminates only when the last-chunk line 0\r\n is followed immediately by the empty trailer line \r\n. RFC 9112 §7.1.2 permits zero or more trailer fields between them. When trailers are present, none of the match clauses fit: the catch-all arm computes a negative to_read, calls read_available!/2, receives <<>> on timeout, and tail-recurses with unchanged state. The worker process is pinned for the lifetime of the TCP connection. A handful of concurrent connections sending RFC-conformant chunked requests with trailer fields is sufficient to exhaust the Bandit worker pool and render the server unresponsive to all further traffic. No authentication, special headers, or large payload is required. Proxies such as NGINX and HAProxy legitimately forward trailer-bearing requests, so servers behind such proxies may be affected without any malicious client involvement. This issue affects bandit: from 1.6.1 before 1.11.1.
Problem types
CWE-835 Loop with Unreachable Exit Condition (‘Infinite Loop’)
Product status
1.6.1 (semver) before 1.11.1
e73e379ab59840e8561b5730878f16e29ab06217 (git) before ae3520dfdbfab115c638f8c7f6f6b805db34e1ab
Credits
Peter Ullrich
Mat Trudel
Jonatan Männchen
References
github.com/…bandit/security/advisories/GHSA-rf5q-vwxw-gmrf
cna.erlef.org/cves/CVE-2026-39806.html
osv.dev/vulnerability/EEF-CVE-2026-39806
github.com/…ommit/ae3520dfdbfab115c638f8c7f6f6b805db34e1ab
