Skip to main content
VulnerabilityPublished Updated

CVE-2026-56811: phoenixframework phoenix · Unthrottled Resource Allocation

Affects phoenixframework phoenixSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High · fixed in 1.8.9 : patch phoenixframework phoenix soon.

Data as of 19 Nov 2026, 20:35 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (EEF)CVSS 4.08.7
EPSS
0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.8.9, 1.7.24, 1.6.17 +1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade phoenixframework phoenix to 1.8.9, 1.7.24, 1.6.17 or 1.5.15.

Affected software

ProductAffectedFixed in
phoenixframeworkphoenixAffected
  • >=1.8.0-rc.0 <1.8.9
Fixed in
  • 1.8.9
phoenixframeworkphoenixAffected
  • >=1.7.0-rc.0 <1.7.24
Fixed in
  • 1.7.24
phoenixframeworkphoenixAffected
  • >=1.6.0-rc.0 <1.6.17
Fixed in
  • 1.6.17
phoenixframeworkphoenixAffected
  • >=0.11.0 <1.5.15
Fixed in
  • 1.5.15
phoenixphoenixframework/phoenixAffected
  • ≥ 14a297e88023cb280a577962a49a0bbdeef9f4eb, < c498ba8cf49f6accbbd0c643a5340b58db891218
Fixed in–
Hexphoenixpkg:hex/phoenixOther threatsAffected
  • >=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
Fixed in
  • 1.5.15
  • 1.6.17
  • 1.7.24
  • 1.8.9

CPE configurations (1)

  • cpe:2.3:a:phoenixframework:phoenix:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The Phoenix framework introduced a :max_channels_per_transport option (defaulting to 100) to limit the number of channels a single transport process can join, mitigating the risk by forcing abusive clients to open multiple connections that can be throttled externally. However, the provided data does not confirm an official patch or remediation level. Users should upgrade to versions 1.5.15, 1.6.17, 1.7.24, or 1.8.9 or later where this option is available.

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.

References

Community reviews

Loading reviews…