Phoenix denial of service via V1 serializer broadcasts
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.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.5.16, 1.6.18, 1.7.25, 1.8.17
- Who is exposed
- Not reported
Summary
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.
Written by a model
Original description
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.
Who should check
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.
“The application must broadcast {:binary, data} payloads”
What to do
Upgrade to a fixed version: 1.5.16, 1.6.18, 1.7.25, 1.8.17.
Workaround: Reject the V1 serializer by listing only the V2 serializer on each socket.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129344 (Client-selected V1 serializer crashes shared broadcast dispatch on binary payloads), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129344 (entry last updated 2026-11-21):
Affected:
- Hex package phoenix: from 1.5.7, fixed in 1.5.16; from 1.6.0-rc.0, fixed in 1.6.18; from 1.7.0-rc.0, fixed in 1.7.25; from 1.8.0-rc.0, fixed in 1.8.17
- phoenixframework phoenix: version range not reported
Fixed versions: 1.5.16, 1.6.18, 1.7.25, 1.8.17.
Conditions (all must be true for the bug to be hit):
- Application broadcasts {:binary, data} payloads on a channel topic (source: https://www.cve.org/CVERecord?id=CVE-2026-129344)
- An untrusted client joins that topic, connecting without a vsn parameter or with vsn=1.0.0 (source: https://cna.erlef.org/cves/CVE-2026-129344.html)
- 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 (source: https://cna.erlef.org/cves/CVE-2026-129344.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Reject the V1 serializer by listing only the V2 serializer on each socket. (source: https://cna.erlef.org/cves/CVE-2026-129344.html)
CISA KEV: CVE-2026-129344 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129344 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Hex): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/phoenixframework/phoenix/security/advisories/GHSA-5vmc-qgf8-rw36
- https://github.com/phoenixframework/phoenix/commit/30e5d9d7704b964772c131314508c45ed85ed807
- https://github.com/phoenixframework/phoenix/commit/5d57f442a1ffab8a866add770477a14a0cd792d9
- https://github.com/phoenixframework/phoenix/commit/c255d983e03893ae46abf01d13c3ec3bd20f029c
- https://github.com/phoenixframework/phoenix/commit/eddaeb6d50c903fc77b465dbf3efd89feee0816b
- https://cna.erlef.org/cves/CVE-2026-129344.html
- https://osv.dev/vulnerability/EEF-CVE-2026-129344
- https://github.com/phoenixframework/phoenix/commit/07b401901fc1d649f126eee6315b5eb01fa5c85c
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129344
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129344"}.Affected versions
- phoenixFrom 1.5.7 · fixed in 1.5.16; From 1.6.0-rc.0 · fixed in 1.6.18; From 1.7.0-rc.0 · fixed in 1.7.25; From 1.8.0-rc.0 · fixed in 1.8.17
- phoenixframework/phoenixVersion range not reported
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects Hex packages
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 40 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 11
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · phoenixframework/phoenix · Advisory GHSA-5vmc-qgf8-rw36 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129344 |
| Record | NVD · CVE-2026-129344 |
| Other links 8 | |
| Patch | GitHub · phoenixframework/phoenix · Commit 30e5d9d7 |
| Patch | GitHub · phoenixframework/phoenix · Commit 5d57f442 |
| Patch | GitHub · phoenixframework/phoenix · Commit c255d983 |
| Patch | GitHub · phoenixframework/phoenix · Commit eddaeb6d |
| Repository | GitHub · phoenixframework/phoenix · Commit 07b40190 |
| Repository | GitHub · phoenixframework/phoenix · Commit cf098e9c |
| Link | cna.erlef.org · cves/CVE-2026-129344.html |
| Link | osv.dev · vulnerability/EEF-CVE-2026-129344 |
Questions about CVE-2026-129344
Is CVE-2026-129344 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
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.
Source: cve.org, cna.erlef.org
Which versions are affected by CVE-2026-129344?
phoenix (Hex): 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; from 1.8.0-rc.0 before 1.8.17.
Source: cve.now feed data
Am I affected, and how do I check?
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.
Source: cve.org, cna.erlef.org
How do I fix CVE-2026-129344?
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.
Source: cve.org, cna.erlef.org
Related
- CVE-2026-56811Phoenix transports do not limit channel joins per connection, enabling process-exhaustion denial of service
- CVE-2026-32689Long-poll NDJSON body splitting causes unbounded memory allocation in Phoenix
- CVE-2026-128361Unsanitized presence key crashes Presence tracker
- CVE-2022-42975socket/transport.ex in Phoenix before 1.6.14 mishandles check_origin wildcarding.
- CVE-2026-56812Phoenix JavaScript presence client crashes on presence keys colliding with Object.prototype members in Presence.syncState/syncDiff
- CVE-2017-1000163The Phoenix Framework versions 1.0.0 through 1.0.4, 1.1.0 through 1.1.6, 1.2.0, 1.2.2 and 1.3.0-rc.0 are vulnerable to unvalidated URL…
No corrections so far. Something wrong on this page? Report an error.