CVE-2026-129344 json
Client-selected V1 serializer crashes shared broadcast dispatch on binary payloads
published yesterday modified 16h ago also EEF-CVE-2026-129344 , GHSA-5vmc-qgf8-rw36 , EUVD-2026-132104
- cvss
- 8.2
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
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.
Patch / fix
- hex phoenix 1.5.16, 1.6.18, 1.7.25, 1.8.17
- phoenixframework phoenix 1.5.16, 1.6.18, 1.7.25, 1.8.17
- github.com/phoenixframework/phoenix@07b4019 commit
- github.com/phoenixframework/phoenix@cf098e9 commit
- github.com/phoenixframework/phoenix@30e5d9d commit
- github.com/phoenixframework/phoenix@5d57f44 commit
- github.com/phoenixframework/phoenix@c255d98 commit
- github.com/phoenixframework/phoenix@eddaeb6 commit
Is CVE-2026-129344 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.2 | 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 |
| OSV | 4.0 | 8.2 | 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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | phoenix | >=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 |
Affected products
- phoenixframework phoenix
Classification
- Weakness
-
- CWE-248 Uncaught Exception
References
-
github.com
/phoenixframework/phoenix/commit/07b401901fc1d649f126eee6315b5eb01fa5c85c
related, web
-
github.com
/phoenixframework/phoenix/commit/cf098e9cf7a44ee6479d31d911a97d3c7430c6fe
related, web
-
github.com
/phoenixframework/phoenix/commit/30e5d9d7704b964772c131314508c45ed85ed807
patch
-
github.com
/phoenixframework/phoenix/commit/5d57f442a1ffab8a866add770477a14a0cd792d9
patch
-
github.com
/phoenixframework/phoenix/commit/c255d983e03893ae46abf01d13c3ec3bd20f029c
patch
-
github.com
/phoenixframework/phoenix/commit/eddaeb6d50c903fc77b465dbf3efd89feee0816b
patch
-
github.com
/phoenixframework/phoenix/security/advisories/GHSA-5vmc-qgf8-rw36
vendor-advisory, related, advisory
-
cna.erlef.org
/cves/CVE-2026-129344.html
related, web
-
osv.dev
/vulnerability/EEF-CVE-2026-129344
related
-
hex.pm
/packages/phoenix
package
Sources
- CVE List CVE-2026-129344
- NVD CVE-2026-129344
- OSV EEF-CVE-2026-129344
- Maintainer advisory GHSA-5vmc-qgf8-rw36
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of phoenixframework/phoenix published their own advisory on GitHub. Reviewed sources take precedence over it.