CVE-2026-129344: Client-selected V1 serializer crashes shared broadcast dispatch on binary payloads

Published Nov 21, 2026
·
Updated

Summary

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.

Details

1. Serializer selection. The socket picks its serializer from the client's vsn parameter. A missing vsn or vsn=1.0.0 selects Phoenix.Socket.V1.JSONSerializer, and Phoenix.Channel.Server registers it as the subscriber's fastlane metadata when the channel joins.

2. Shared dispatch. A broadcast runs Phoenix.Channel.Server.send/4 once per subscriber, inside the PubSub dispatch loop of the broadcasting process. It encodes the message with each subscriber's serializer through fastlane!/1 and has no rescue.

3. Crash. Phoenix.Socket.V1.JSONSerializer.fastlane!/1 JSON-encodes the payload, so a {:binary, data} tuple raises Protocol.UndefinedError. The exception aborts the loop: the broadcasting channel crashes (its client receives phxerror) and every subscriber after the attacker misses the message.

4. Cluster spread. For broadcasts from other nodes, the same loop runs in the Phoenix.PubSub.PG2 adapter worker. Each forwarded binary broadcast crashes it, and repeated crashes exceed the restart intensity and restart the PubSub supervisor, which empties the subscription registry while sockets stay connected. The report simulated this step locally by sending :forwardtolocal to the worker.

Proof of concept

1. Run a Phoenix endpoint with a channel whose handlein/3 calls broadcast(socket, "evt", {:binary, <<0, 1, 2, 3>>}) on its topic. 2. As the attacker, open /socket/websocket?vsn=1.0.0 and join the topic with a V1 frame ({"topic": ..., "event": "phxjoin", "payload": {}, "ref": ...}). 3. Connect several V2 clients (vsn=2.0.0) and join the same topic. 4. From another V2 client on the topic, push the event that triggers the binary broadcast. 5. The broadcaster receives phxerror, the log shows Protocol.UndefinedError raised from Phoenix.Socket.V1.JSONSerializer.fastlane!/1 through Phoenix.Channel.Server.send/4, and the V2 subscribers after the attacker receive nothing. Without the attacker, the same broadcast reaches every subscriber.

Impact

An attacker who can join a topic makes every binary broadcast on it fail, crashing the broadcasting channel and starving the other subscribers. In clustered deployments, forwarded broadcasts crash the PubSub adapter worker until the node's subscriptions are lost.

Workarounds

Reject the V1 serializer by listing only the V2 serializer on each socket:

elixir 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.

Configurations

The application must broadcast {:binary, data} payloads (through Phoenix.Channel.broadcast/3, broadcastfrom/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.

Other sources

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.

— MITRE

Affected Software

4 affected componentsFixes available
erlang/phoenix>=1.5.7<1.5.16
1.5.16
erlang/phoenix>=1.6.0-rc.0<1.6.18
1.6.18
erlang/phoenix>=1.7.0-rc.0<1.7.25
1.7.25
erlang/phoenix>=1.8.0-rc.0<1.8.17
1.8.17

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade erlang/phoenix to a version that resolves this vulnerability.

    Fixed in 1.5.16
  2. Upgrade

    Upgrade erlang/phoenix to a version that resolves this vulnerability.

    Fixed in 1.6.18
  3. Upgrade

    Upgrade erlang/phoenix to a version that resolves this vulnerability.

    Fixed in 1.7.25
  4. Upgrade

    Upgrade erlang/phoenix to a version that resolves this vulnerability.

    Fixed in 1.8.17
  5. Upgrade

    Upgrade phoenix to a version that resolves this vulnerability.

    Fixed in 1.5.16
  6. Upgrade

    Upgrade phoenix to a version that resolves this vulnerability.

    Fixed in 1.6.18
  7. Upgrade

    Upgrade phoenix to a version that resolves this vulnerability.

    Fixed in 1.7.25
  8. Upgrade

    Upgrade phoenix to a version that resolves this vulnerability.

    Fixed in 1.8.17
  9. Configuration

    List only Phoenix.Socket.V2.JSONSerializer for both websocket and longpoll socket serializers so clients cannot select the V1 serializer.

    Phoenix socket serializer = [{Phoenix.Socket.V2.JSONSerializer, "~> 2.0.0"}]

Event History

Nov 21, 2026
CVE Published
via MITRE·10:59 AM
Data Sourced
via MITRE·10:59 AM
DescriptionWeakness
Data Sourced
via OSV·10:59 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeakness

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203