Skip to content
Threat Brief

← All advisories

CVE-2026-56811

High 8.7No known exploitationFix available

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

Record last updated

CVSS score

8.7

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.8%

Higher than 57% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-770

Patching and mitigation

Patch status
Fix available (source: NVD (reference tagged Patch))
Fix documented (source date)
Mitigation
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. Source (opens in a new tab)
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
phoenixframeworkphoenixfrom 0.11.0 before 1.5.151.5.15CVE Program
phoenixframeworkphoenixfrom 1.2.0 before 1.5.151.5.15NIST NVD
phoenixframeworkphoenixfrom 1.6.0 before 1.6.171.6.17NIST NVD
phoenixframeworkphoenixfrom 1.6.0-rc.0 before 1.6.171.6.17CVE Program
phoenixframeworkphoenixfrom 1.7.0 before 1.7.241.7.24NIST NVD
phoenixframeworkphoenixfrom 1.7.0-rc.0 before 1.7.241.7.24CVE Program
phoenixframeworkphoenixfrom 1.8.0 before 1.8.91.8.9NIST NVD
phoenixframeworkphoenixfrom 1.8.0-rc.0 before 1.8.91.8.9CVE Program
phoenixframeworkphoenix14a297e88023cb280a577962a49a0bbdeef9f4ebNot documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by NVD (reference tagged Patch)

    Source: NVD (reference tagged Patch) (opens in a new tab)

Vendor guidance and references