Answer in brief
CVE-2026-129344 records a High severity (CVSS 8.2) vulnerability in Client-selected V1 serializer crashes shared broadcast dispatch on binary payloads. The current sources do not mark it as known exploited. The current feed maps phoenixframework/phoenix (generic), phoenixframework/phoenixframework/phoenix (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps phoenixframework/phoenix (generic), phoenixframework/phoenixframework/phoenix (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| phoenixframework/phoenixgeneric | >=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 | 1.5.16, 1.6.18, 1.7.25, 1.8.17 |
| phoenixframework/phoenixframework/phoenixgeneric | >=07b401901fc1d649f126eee6315b5eb01fa5c85c <c255d983e03893ae46abf01d13c3ec3bd20f029c || >=cf098e9cf7a44ee6479d31d911a97d3c7430c6fe <* | c255d983e03893ae46abf01d13c3ec3bd20f029c, * |
Published upstream
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.