cve.bz

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

8.7 highEPSS 0.8%Fix available

High (8.7) in phoenixframework phoenix. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in phoenix 1.5.15, 1.6.17, 1.7.24.

On this page
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.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 57th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-07-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
Assigned by
EEF (CNA)
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-56811 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-56811?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-56811?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-56811 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
phoenixframework phoenixfrom 0.11.0 before 1.5.15
phoenixframework phoenixfrom 1.6.0-rc.0 before 1.6.17
phoenixframework phoenixfrom 1.7.0-rc.0 before 1.7.24
phoenixframework phoenixfrom 1.8.0-rc.0 before 1.8.9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-56811Hexphoenix>=0.11.0 <1.5.15
>=1.6.0-rc.0 <1.6.17
>=1.7.0-rc.0 <1.7.24
>=1.8.0-rc.0 <1.8.9
1.5.15, 1.6.17, 1.7.24, 1.8.9
EEF-CVE-2026-56811no fix published
GHSA-6983-jfq8-485wHexphoenix>=0.11.0 <1.5.151.5.15
GHSA-6983-jfq8-485wHexphoenix>=1.6.0-rc.0 <1.6.171.6.17
GHSA-6983-jfq8-485wHexphoenix>=1.7.0-rc.0 <1.7.241.7.24
GHSA-6983-jfq8-485wHexphoenix>=1.8.0-rc.0 <1.8.91.8.9

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON