CVE-2026-128361
- Published21 Nov 2026
Description
Improper Input Validation vulnerability in phoenixframework phoenix (Phoenix.Presence) allows an attacker who can join a channel to cause a denial of service via a non-string presence key. track/3,4 accepts any term as the presence key, such as a JSON object taken from a join payload. The key is converted with to_string/1 only later, in Phoenix.Presence.group/1, which raises Protocol.UndefinedError on a map. group/1 runs whenever presences are listed and when each presence diff is broadcast, together with the application's fetch/2, which can likewise raise on an unexpected key. Once such a key is tracked, every process that lists presences on the topic crashes, typically each channel that joins it, and presence diffs for the topic are lost. From 1.7.0 the diff runs in a Task.Supervisor.async task linked to the tracker shard, and Phoenix.Presence.handle_info/2 has no clause for its failure. The shard then terminates, taking down every channel and LiveView process tracked on it and erasing presence state for all its topics. Repeated joins exhaust the restart intensity and take down the application supervisor. This issue affects phoenix: from 1.2.0 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.
CVSS 4.0 breakdown
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://cna.erlef.org/cves/CVE-2026-128361.html
- https://github.com/phoenixframework/phoenix/commit/39c1c6bfd0c817f1223c121f61c60a25f66b76cb
- https://github.com/phoenixframework/phoenix/commit/44e7618370629df93711cd6169789fd0d8f3678e
- https://github.com/phoenixframework/phoenix/commit/6609595fb3e37f545c4ac636a369f14b0084bc3d
- https://github.com/phoenixframework/phoenix/commit/81bc0278c7a4e6204f7e2e0a3b3200e9f1ee5a4b
- https://github.com/phoenixframework/phoenix/commit/edb702804aeab3a29543668a8be8ea61291c4b75
- https://github.com/phoenixframework/phoenix/security/advisories/GHSA-pvfx-rx4x-phrr
- https://osv.dev/vulnerability/EEF-CVE-2026-128361
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-128361 being actively exploited?
CVE-2026-128361 is not in the CISA KEV catalog.
How severe is CVE-2026-128361?
CVE-2026-128361 has a CVSS 4.0 base score of 8.2, rated high.
How do I fix CVE-2026-128361?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-128361 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. The CVSS 4.0 base score is shown where the NVD has one, otherwise CVSS 3.1.