llamaCVEVulnerability Intelligence
/
phoenix

CVE-2026-56811

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

Afecta la configuración por defectoParche disponibledenial of service
Descargar PNG JSON
CVSS 4.0
8.7
Alta
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 Fuente: CNA
7.5NVD · CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
ExplotaciónSin evidenciaSSVC: ninguna · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche4 versiones1.5.15 · 1.6.17 · 1.7.24 · 1.8.9
Exposición136 dDesde la divulgación, 7 jul 2026, 10:09 a. m.
Detección107 dDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Modificada
Explotación
Remediación
Monitoreo
Detectada
Fuente: OSV
Fuente: NIST NVD +1
7 jul 26
22 oct 26
24 oct 26
20 nov 26
21 nov 26
7 jul 26
10 ago 26
13 sept 26
18 oct 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-56811 divulgada · CVSS 8.7 (CNA)
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Divulgación Modificada Última actualización del registro
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Monitoreo Verificada Última verificación contra las fuentes
Resumen

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.

¿Qué significa?Phoenix transports do not limit how many channel joins one connection can make. An unauthenticated remote client can open many channel joins over WebSocket or LongPoll and exhaust BEAM processes, so the node can no longer start new ones, causing a denial of service.
¿Quién está afectado?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. The application must mount a Phoenix socket that defines channels and expose it over HTTP so a client can reach a WebSocket or LongPoll transport and send phx_join messages; applications that do not mount a socket with channels are not affected. Check the Phoenix version in the project's mix.lock or deps list, and check whether the endpoint declares socket routes with channels.
¿Qué hacer?Upgrade Phoenix to 1.5.15, 1.6.17, 1.7.24, or 1.8.9, whichever matches your release line. No vendor patch identifiers are listed in the facts.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
The application mounts a Phoenix socket that defines channels and exposes it over HTTP so a client can reach a channel transport (WebSocket or LongPoll) and send phx_join messages.“The application must mount a Phoenix socket that defines channels and expose it over HTTP”
02
Applications that do not mount a socket with channels are not affected.“Applications that do not mount a socket with channels are not affected.”
¿Quién debe revisar?Teams running Phoenix sockets with channels over WebSocket or LongPoll transports on phoenix 0.11.0 up to the patched 1.5.15, 1.6.17, 1.7.24 or 1.8.9 releases, including Hex phoenix users.
MitigaciónFront 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.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · NVD
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:N
AltoBajoNinguno
IntegridadI:N
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
10.0/ 10Muy alto
Vector 10.0 (muy fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida
phoenix≥ 0.11.0 < 1.5.15
phoenix≥ 1.6.0-rc.0 < 1.6.17
phoenix≥ 1.7.0-rc.0 < 1.7.24
phoenix≥ 1.8.0-rc.0 < 1.8.9
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
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
phoenix
Corregida 1.5.15, 1.6.17, 1.7.24, 1.8.9 — —
Versiones corregidas1.5.151.6.171.7.241.8.9
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Registro
EscenarioGENERALEEF
configurationThe application must mount a Phoenix socket that defines channels and expose it over HTTP so that a client can reach a channel transport (WebSocket or LongPoll) and send phx_join messages. The WebSocket transport is enabled by default on a mounted socket, while the LongPoll transport is opt-in. Applications that do not mount a socket with channels are not affected.EEF
MitigaciónFront 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.EEF
Referencias
Fabricantehttps://github.com/phoenixframework/phoenix/security/advisories/GHSA-6983-jfq8-485w
Parchehttps://github.com/phoenixframework/phoenix/commit/16e295d2fccab185d1292322e2bee5d46c725c8a
Parchehttps://github.com/phoenixframework/phoenix/commit/a612100cd8a4279091abc1a2ef8fb98a6d01c0a1
Parchehttps://github.com/phoenixframework/phoenix/commit/c498ba8cf49f6accbbd0c643a5340b58db891218
Parchehttps://github.com/phoenixframework/phoenix/commit/d19ca0a8d9f82c130b7ed339b9f033433e2dea5e
Otrahttps://cna.erlef.org/cves/CVE-2026-56811.html
Otrahttps://osv.dev/vulnerability/EEF-CVE-2026-56811
Otrahttps://github.com/phoenixframework/phoenix/commit/14a297e88023cb280a577962a49a0bbdeef9f4eb

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.