CVE-2026-56811Phoenix transports do not limit channel joins per connection, enabling process-exhaustion denial of service
- 8.7HighCVSS base score
- 0.78%Exploitation in 30 daysEPSS · top 44% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By EEF
- 14 days later
· 14 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| EEFCNA (assigner) | 4.0 | High8.7 | 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 |
| NVDNVD · Modified | 4.0 | High8.7 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
- EPSS (exploitation in 30 days)
- 0.78% · top 44% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.7.
Affected products
- affected 0.11.0 – < 1.5.15
- affected 1.6.0-rc.0 – < 1.6.17
- affected 1.7.0-rc.0 – < 1.7.24
- affected 1.8.0-rc.0 – < 1.8.9
- affected 14a297e88023cb280a577962a49a0bbdeef9f4eb – < *
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- HexphoenixGHSA-6983-jfq8-485w (opens in a new tab)
What to do
Workaround: 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.
References
References8
- https://github.com/phoenixframework/phoenix/security/advisories/GHSA-6983-jfq8-485w (opens in a new tab)vendor-advisoryrelated
- EEF CNA record for CVE-2026-56811 (opens in a new tab)related
- OSV record EEF-CVE-2026-56811 (opens in a new tab)related
- Introducing commit 14a297e in phoenixframework/phoenix (opens in a new tab)related
- Fix commit c498ba8 in phoenixframework/phoenix (opens in a new tab)patch
- Fix commit d19ca0a in phoenixframework/phoenix (opens in a new tab)patch
- Fix commit a612100 in phoenixframework/phoenix (opens in a new tab)patch
- Fix commit 16e295d in phoenixframework/phoenix (opens in a new tab)patch
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-42049 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-6983-jfq8-485w (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-56811)Record last updated .