llamaCVEVulnerability Intelligence
/
Phoenix

CVE-2026-129344

Phoenix denial of service via V1 serializer broadcasts

An unauthenticated attacker can crash binary broadcasts, skipping other subscribers and restarting PubSub.

Texto original en inglés · Ver en español

UnclearParche disponibleuncaught exception
Descargar PNG JSON
CVSS 4.0
8.2
Alta
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N Fuente: CNA
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche4 versiones1.5.16 · 1.6.18 · 1.7.25 · 1.8.17
Exposición10 hDesde la divulgación, 21 nov 2026, 5:59 a. m.
Detección4 minDesde la divulgación hasta su ingreso al índice
Decisión estimadaSeguir
Remediar en la ventana regular de mantenimiento
Estimación de Llama con el árbol SSVC de CISA a partir de vector CVSS 4.0 y la evidencia de explotación (sin evaluación oficial): sin explotación conocida, no automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Revisa si tu versión cae en el rango. Te espero.Sospechosa como un adjunto llamado factura_final2.exe.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada +2
05:59 a. m.
06:03 a. m.
03:40 p. m.
05:59 a. m.
08:24 a. m.
10:49 a. m.
01:15 p. m.
03:40 p. m.
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-129344 divulgada · CVSS 8.2 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 21 nov 2026

The phoenix framework has a flaw that lets an unauthenticated attacker over the network cause a denial of service. A client that selects the legacy V1 serializer and joins a channel topic that receives binary broadcasts makes those broadcasts crash, which skips other subscribers and can restart the PubSub supervisor.

Affects Phoenix 1.5.7 to before 1.5.16, 1.6.0-rc.0 to before 1.6.18, 1.7.0-rc.0 to before 1.7.25, and 1.8.0-rc.0 to before 1.8.17 when binary broadcasts go to a topic. Fixed in 1.5.16, 1.6.18, 1.7.25, and 1.8.17.

¿Qué significa?A client that connects with the V1 serializer, either without a vsn parameter or with vsn=1.0.0, can crash shared broadcast dispatch when the application sends {:binary, data} payloads on that topic. Every binary broadcast on the affected topic then fails, and in clustered deployments the node's PubSub subscription registry can be emptied.
¿Quién está afectado?Affected versions are Phoenix 1.5.7 to before 1.5.16, 1.6.0-rc.0 to before 1.6.18, 1.7.0-rc.0 to before 1.7.25, and 1.8.0-rc.0 to before 1.8.17. The issue needs an application that broadcasts {:binary, data} payloads on a channel topic and sockets that accept the V1 serializer; the Phoenix version can be checked in the project's mix.lock or with mix deps.
¿Qué hacer?Upgrade Phoenix to 1.5.16, 1.6.18, 1.7.25, or 1.8.17, matching the release line in use. Until the upgrade is applied, the workaround is to list only the V2 serializer on each socket so V1 is rejected.
Descripción original del registro (EEF)

Uncaught Exception vulnerability in phoenixframework phoenix allows an unauthenticated attacker to cause a denial of service via a client-selected legacy serializer on binary channel broadcasts. When an application broadcasts {:binary, data} payloads on a channel topic, any client that connects without a vsn parameter, or with vsn=1.0.0, and joins that topic makes those broadcasts fail. Phoenix.Channel.Server.send/4 encodes each broadcast with every subscriber's own serializer inside the PubSub dispatch loop, calling fastlane!/1 with no rescue, and the negotiated Phoenix.Socket.V1.JSONSerializer raises Protocol.UndefinedError on a binary payload. Every binary broadcast on the topic then crashes the broadcasting process and skips every subscriber dispatched after the attacker. For broadcasts arriving from other nodes the loop runs in the PubSub adapter worker, whose repeated crashes restart the PubSub supervisor and empty the node's subscription registry while sockets stay connected. This issue affects phoenix: from 1.5.7 before 1.5.16, from 1.6.0-rc.0 before 1.6.18, from 1.7.0-rc.0 before 1.7.25, and from 1.8.0-rc.0 before 1.8.17.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Application broadcasts {:binary, data} payloads on a channel topic“The application must broadcast {:binary, data} payloads”
02
An untrusted client joins that topic, connecting without a vsn parameter or with vsn=1.0.0“any client that connects without a vsn parameter, or with vsn=1.0.0”
03
Affected Phoenix versions: 1.5.7 to before 1.5.16, 1.6.0-rc.0 to before 1.6.18, 1.7.0-rc.0 to before 1.7.25, 1.8.0-rc.0 to before 1.8.17“This issue affects phoenix: from 1.5.7 before 1.5.16”
¿Quién debe revisar?Teams running Phoenix 1.5.7 through 1.5.x before 1.5.16, 1.6 before 1.6.18, 1.7 before 1.7.25, or 1.8 before 1.8.17 that broadcast {:binary, data} payloads on channel topics clients can join.
MitigaciónReject the V1 serializer by listing only the V2 serializer on each socket.
Vector CVSS 4.0

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
Requisitos de ataqueAT:P
NingunoPresentes
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaPasivaActiva
Confid. (sistema)VC:N
AltoBajoNinguno
Integridad (sistema)VI:N
AltoBajoNinguno
Disponib. (sistema)VA:H
AltoBajoNinguno
Confid. (posterior)SC:N
AltoBajoNinguno
Integridad (posterior)SI:N
AltoBajoNinguno
Disponib. (posterior)SA:N
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
7.1/ 10Alto
Vector 7.1 (fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida
phoenix< 1.5.16
phoenix< 1.6.18
phoenix< 1.7.25
phoenix< 1.8.17
phoenix≥ 1.5.7 < 1.5.16
phoenix≥ 1.6.0-rc.0 < 1.6.18
phoenix≥ 1.7.0-rc.0 < 1.7.25
phoenix≥ 1.8.0-rc.0 < 1.8.17
1.5.7
1.5.16
1.6.0-rc.0
1.6.18
1.7.0-rc.0
1.7.25
1.8.0-rc.0
1.8.17
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
phoenix
Corregida 1.5.16, 1.6.18, 1.7.25, 1.8.17 — —
Versiones corregidas1.5.161.6.181.7.251.8.17
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 broadcast {:binary, data} payloads (through Phoenix.Channel.broadcast/3, broadcast_from/3, or Phoenix.Endpoint.broadcast/3) on a channel topic that an untrusted client can join. Applications that broadcast only map payloads are not affected.EEF
MitigaciónReject the V1 serializer by listing only the V2 serializer on each socket: socket "/socket", MyAppWeb.UserSocket, websocket: [serializer: [{Phoenix.Socket.V2.JSONSerializer, "~> 2.0.0"}]], longpoll: [serializer: [{Phoenix.Socket.V2.JSONSerializer, "~> 2.0.0"}]] Clients that connect without a vsn parameter or with vsn=1.0.0 are then refused.EEF
Referencias
Fabricantehttps://github.com/phoenixframework/phoenix/security/advisories/GHSA-5vmc-qgf8-rw36
Parchehttps://github.com/phoenixframework/phoenix/commit/30e5d9d7704b964772c131314508c45ed85ed807
Parchehttps://github.com/phoenixframework/phoenix/commit/5d57f442a1ffab8a866add770477a14a0cd792d9
Parchehttps://github.com/phoenixframework/phoenix/commit/c255d983e03893ae46abf01d13c3ec3bd20f029c
Parchehttps://github.com/phoenixframework/phoenix/commit/eddaeb6d50c903fc77b465dbf3efd89feee0816b
Otrahttps://cna.erlef.org/cves/CVE-2026-129344.html
Otrahttps://osv.dev/vulnerability/EEF-CVE-2026-129344
Otrahttps://github.com/phoenixframework/phoenix/commit/07b401901fc1d649f126eee6315b5eb01fa5c85c
Otrahttps://github.com/phoenixframework/phoenix/commit/cf098e9cf7a44ee6479d31d911a97d3c7430c6fe

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