8.7

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

Modified
Published 07-07-2026Last modified 20-11-2026

Vulnerability summary

CVE-2026-56811 is a high (CVSS 8.7) vulnerability in phoenixframework phoenix. EPSS estimates a 0.78% chance of exploitation in the next 30 days, higher than 56.6% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 8.7 (CVE.org); no exploitation reported by the 5 checked sources; EPSS 1% (FIRST, 20-11-2026)

Source freshness unavailable

How is this decided?
CVSS score
8.7/10
010
High · v4.0 (CVE.org)
EPSS score
0.78%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Timeline

  1. 07-07-2026
    PublishedVulnerability first disclosed.
  2. 20-11-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

3 scores · 2 sources · 2 versions

EPSS trend

Probability

0.78%

Chance of exploitation in the next 30 days

Percentile

57%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.78% on 21-10-2026

21-10-202620-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Phoenixframework1 product
  • phoenix≥ 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 | ≥ 14a297e88023cb280a577962a49a0bbdeef9f4eb (No fix recorded) | ≥ 1.2.0, < 1.5.15 | ≥ 1.6.0, < 1.6.17 | ≥ 1.7.0, < 1.7.24 | ≥ 1.8.0, < 1.8.9

1 vendor · 1 product

References

8 links