cve.bz

CVE-2026-128361 Unsanitized presence key crashes Presence tracker

8.2 highEPSS 0.6%Fix available

High (8.2) in phoenixframework phoenix. EPSS 0.6% 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
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.

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.6% estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
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-128361 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128361?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128361?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-128361 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.2.0 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-128361Hexphoenix>=1.2.0 <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-128361v1.5.15, v1.6.17, v1.7.24, v1.8.16, v1.8.15 and 88 moreno fix published

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON