Vulnerability EEF-CVE-2026-56811

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
4 months ago
July 07, 2026 at 03:09 PM UTC
Phoenix transports do not limit channel joins per connection, enabling process-exhaustion denial of service
0.11.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8
0.11.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8

Summary

Phoenix transports do not limit channel joins per connection, enabling process-exhaustion denial of service

Details

Summary

Allocation of Resources Without Limits or Throttling vulnerability in phoenixframework phoenix (Phoenix.Socket module) allows an unauthenticated attacker to cause a denial of service against any endpoint that mounts a Phoenix socket with a reachable channel transport (WebSocket or LongPoll).

This vulnerability is associated with program files lib/phoenix/socket.ex and program routine 'Elixir.Phoenix.Socket':handle_in/4.

Phoenix transports do not limit the number of channels that a single transport process may join. Every phx_join message a client sends over one connection starts a persistent channel process, and the socket process accepts an unbounded number of them. A single unauthenticated client can therefore open one WebSocket or LongPoll connection and stream a large number of phx_join messages, spawning hundreds of thousands of channel processes over that one connection and eventually reaching the BEAM maximum process limit. Once the process table is exhausted the virtual machine can no longer start new processes, denying service to legitimate traffic across the whole node. Because the amplification happens inside a single connection, network-layer connection caps and rate limiting do not mitigate it.

The fix adds a :max_channels_per_transport option (default 100) that bounds the number of channels a single transport process can join, forcing abusive clients to open many connections instead, where external load balancers and reverse proxies can throttle them.

This issue affects phoenix: from 0.11.0 before 1.5.15, from 1.6.0-rc.0 before 1.6.17, from 1.7.0-rc.0 before 1.7.24, and from 1.8.0-rc.0 before 1.8.9.

Workarounds

Front the socket endpoint with a reverse proxy that limits the number and rate of channel-join frames per connection, or disable transports that are not needed (for example remove longpoll: true from the socket declaration where the LongPoll transport is not required). Lowering the BEAM +P maximum process limit does not prevent the exhaustion and can make it easier to trigger.

Configurations

The application must mount a Phoenix socket that defines channels and expose it over HTTP so that a client can reach a channel transport (WebSocket or LongPoll) and send phx_join messages. The WebSocket transport is enabled by default on a mounted socket, while the LongPoll transport is opt-in. Applications that do not mount a socket with channels are not affected.

Related Vulnerabilities

Other vulnerabilities affecting the same packages

Unknown
1 day ago
Unsanitized presence key crashes Presence tracker
1.2.0 - 1.5.15 and 1.6.0-rc.0 - 1.6.17 and 1.7.0-rc.0 - 1.7.24 and 1.8.0-rc.0 - 1.8.16 EEF-CVE-2026-128361
1.2.0 - 1.5.15 and 1.6.0-rc.0 - 1.6.17 and 1.7.0-rc.0 - 1.7.24 and 1.8.0-rc.0 - 1.8.16 EEF-CVE-2026-128361
Unknown
1 day ago
Client-selected V1 serializer crashes shared broadcast dispatch on binary payloads
1.5.7 - 1.5.15 and 1.6.0-rc.0 - 1.6.17 and 1.7.0-rc.0 - 1.7.24 and 1.8.0-rc.0 - 1.8.16 EEF-CVE-2026-129344
1.5.7 - 1.5.15 and 1.6.0-rc.0 - 1.6.17 and 1.7.0-rc.0 - 1.7.24 and 1.8.0-rc.0 - 1.8.16 EEF-CVE-2026-129344
High Risk
2 months ago
Phoenix: Unbounded channel joins per transport enables DoS over few connections
0.11.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 GHSA-6983-jfq8-485w
0.11.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 GHSA-6983-jfq8-485w
Medium Risk
2 months ago
Phoenix: Presence keys colliding with `Object.prototype` members break existence checks
1.2.0-rc.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 GHSA-63mc-hw7g-86rr
1.2.0-rc.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 GHSA-63mc-hw7g-86rr
Unknown
4 months ago
Phoenix JavaScript presence client crashes on presence keys colliding with Object.prototype members in Presence.syncState/syncDiff
1.2.0-rc.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 EEF-CVE-2026-56812
1.2.0-rc.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 EEF-CVE-2026-56812
View all vulnerabilities for these packages

Impacted packages

Timeline

Published
4 months ago
July 07, 2026 at 03:09 PM UTC
Fixed (1.8.9)
4 months ago
July 07, 2026 at 12:23 PM UTC
Fixed (1.7.24)
4 months ago
July 07, 2026 at 12:25 PM UTC
Fixed (1.6.17)
4 months ago
July 07, 2026 at 12:53 PM UTC
Fixed (1.5.15)
4 months ago
July 07, 2026 at 12:56 PM UTC
Last Modified
2 days ago
November 20, 2026 at 06:15 AM UTC