cve.bz

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

8.2 highEPSS 0.7%Fix available

High (8.2) in phoenixframework phoenix. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in phoenix 1.5.16, 1.6.18, 1.7.25.

On this page
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.

Severity

CVSS 4.0

8.2 high
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
EPSS
0.7% estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-248 Uncaught Exception
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Assigned by
EEF (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • phoenix (Hex): fixed in 1.5.16, 1.6.18, 1.7.25, 1.8.17

Ask an AI about this CVE

Show the promptExplain CVE-2026-129344 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-129344?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-129344?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-129344 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
phoenixframework phoenixfrom 1.5.7 before 1.5.16
phoenixframework phoenixfrom 1.6.0-rc.0 before 1.6.18
phoenixframework phoenixfrom 1.7.0-rc.0 before 1.7.25
phoenixframework phoenixfrom 1.8.0-rc.0 before 1.8.17

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-129344Hexphoenix>=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
EEF-CVE-2026-129344v1.5.15, v1.5.13, v1.5.12, v1.5.11, v1.5.10 and 69 moreno fix published

References

Check your stackJSON