Vulnerability · Published Mar 20, 2026 · Assigned by GitHub_M
CVE-2026-32873ewe: Loop with Unreachable Exit Condition ('Infinite Loop')
High 7.5
In plain English
A high-severity security flaw in ewe from vshakitskiy. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 50% of all known vulnerabilities).
Official description
ewe is a Gleam web server. Versions 0.8.0 through 3.0.4 contain a bug in the handle_trailers function where rejected trailer headers (forbidden or undeclared) cause an infinite loop. When handle_trailers encounters such a trailer, three code paths (lines 520, 523, 526) recurse with the original buffer (rest) instead of advancing past the rejected header (Buffer(header_rest, 0)), causing decoder.decode_packet to re-parse the same header on every iteration. The resulting loop has no timeout or escape — the BEAM process permanently wedges at 100% CPU. Any application that calls ewe.read_body on chunked requests is affected, and this is exploitable by any unauthenticated remote client before control returns to application code, making an application-level workaround impossible. This issue is fixed in version 3.0.5.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| vshakitskiy | ewe | >= 0.8.0, < 3.0.5 |
Weakness: CWE-825 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H