PT-2026-153833
CVE-2026-128361
·
Published
2026-11-21
·
Updated
2026-11-21
Description by
CVSS 4.0
8.2
HighMetricsAV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Name of the Vulnerable Software and Affected Versions
phoenix versions 1.2.0 through 1.5.15
phoenix versions 1.6.0-rc.0 through 1.6.17
phoenix versions 1.7.0-rc.0 through 1.7.24
phoenix versions 1.8.0-rc.0 through 1.8.16
Description
Improper input validation in
Phoenix.Presence allows an attacker who can join a channel to cause a denial of service by providing a non-string presence key. The track/3,4 function accepts any term as a presence key, such as a JSON object from a join payload. This key is later processed by Phoenix.Presence.group/1 using to string/1, which raises a Protocol.UndefinedError when a map is encountered. This failure occurs during presence listing or when presence diffs are broadcast, and can also be triggered by the application's fetch/2 function if it raises on an unexpected key.In versions 1.7.0 and later, the diff runs in a
Task.Supervisor.async task linked to the tracker shard. Because Phoenix.Presence.handle info/2 lacks a failure clause, the shard terminates, crashing all linked channels and LiveView processes and erasing presence state for all topics. Repeated exploitation can exhaust the restart intensity and crash the application supervisor.Recommendations
Update phoenix to version 1.5.16, 1.6.18, 1.7.25, or 1.8.17 depending on the current version branch.
Validate every presence key before passing it to
track/3,4, untrack/2,3, or update/3,4 to ensure only strings reach the tracker.
Reject join requests where the presence key value is not a binary or explicitly convert it to a string.
Ensure the fetch/2 callback is implemented so that it does not raise an error on any tracked key.Exploitability
Exploit
Fix
Impacts
Vendors
Affected products
Found an issue in the description? Have something to add? Feel free to write us 👾