Phoenix (>= 1.7.0-Rc.0, < 1.7.24) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/phoenix--1.7.0-rc.0--1.7.24/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 04 Sep 2026 00:05:32 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgPhoenix Transport Channel Exhaustion Denial of Servicehttps://feed.craftedsignal.io/briefs/2026-09-phoenix-dos/Fri, 04 Sep 2026 00:05:32 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-phoenix-dos/The Phoenix web framework lacks limits on channels per transport, allowing an unauthenticated attacker to cause a DoS by exhausting Erlang VM process limits via CVE-2026-56811.The Phoenix web framework is vulnerable to a denial of service (DoS) condition due to an unbounded number of concurrent channel joins allowed over a single transport connection (LongPoll or WebSocket). By initiating a single connection, an unauthenticated remote attacker can programmatically trigger the creation of hundreds of thousands of Erlang processes. This behavior rapidly consumes system resources, eventually exceeding the Erlang VM's maximum process limit and resulting in a service crash. The issue, tracked as CVE-2026-56811, affects various versions across the 1.5, 1.6, 1.7, and 1.8 release branches. Defenders should note that because the exhaustion occurs within the application transport layer, standard infrastructure rate limiting may be ineffective unless applied at the connection level rather than the channel level.

Impact

Successful exploitation results in a complete denial of service for any Phoenix-based application exposing LongPoll or WebSocket transports. As this does not require authentication, any internet-facing Phoenix instance is susceptible to resource exhaustion, potentially impacting critical production systems and causing significant downtime until the service is manually restarted or mitigated via patching.

Recommendation

  1. Patch Phoenix immediately to the corrected versions: v1.5.15, v1.6.17, v1.7.24, or v1.8.9.
  2. Implement aggressive rate limiting on connection establishment at the load balancer or reverse proxy level to mitigate the impact of rapid connection cycles.
  3. Monitor Erlang VM metrics, specifically process counts and memory usage, for anomalous spikes that do not correlate with legitimate user traffic volume.
]]>lowadvisorydenial-of-serviceweb-frameworkcve-2026-56811