Answer in brief
CVE-2026-128361 records a High severity (CVSS 8.2) vulnerability in Unsanitized presence key crashes Presence tracker. The current sources do not mark it as known exploited. The current feed maps phoenixframework/phoenix (generic), phoenixframework/phoenixframework/phoenix (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps phoenixframework/phoenix (generic), phoenixframework/phoenixframework/phoenix (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| phoenixframework/phoenixgeneric | >=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 |
| phoenixframework/phoenixframework/phoenixgeneric | >=44e7618370629df93711cd6169789fd0d8f3678e <* | * |
Published upstream
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.