Phoenix denial of service in presence tracker
Only affects Phoenix apps using Phoenix.Presence that track presences under a client-influenced key, from 1.2.0 up to the fixed releases. Fixed in 1.5.16, 1.6.18, 1.7.25 and 1.8.17, depending on series.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.5.16, 1.6.18, 1.7.25, 1.8.17
- Who is exposed
- Not reported
Summary
The phoenixframework phoenix software's presence tracking (Phoenix.Presence) can be crashed by an attacker who can join a channel. Attackers can do this remotely and without logging in, by sending a non-string presence key such as a JSON object, which takes down the tracker and the channel and LiveView processes on that topic.
Written by a model
Original 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.
Who should check
Teams running Phoenix 1.2 to 1.8 (Hex phoenix) that track Phoenix.Presence keys from client input such as join payloads, or use a fetch/2 callback that can raise.
Not fixed by: A fetch/2 callback must also not raise on any tracked key.
“The application must use Phoenix.Presence”
What to do
Upgrade to a fixed version: 1.5.16, 1.6.18, 1.7.25, 1.8.17.
Workaround: Validate every presence key before passing it to track/3,4, untrack/2,3 or update/3,4, so that only strings reach the tracker.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128361 (Unsanitized presence key crashes Presence tracker), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128361 (entry last updated 2026-11-21):
Affected:
- Hex package phoenix: from 1.2.0, fixed in 1.5.16; from 1.6.0-rc.0, fixed in 1.6.18; from 1.7.0-rc.0, fixed in 1.7.25; from 1.8.0-rc.0, fixed in 1.8.17
- phoenixframework phoenix: version range not reported
Fixed versions: 1.5.16, 1.6.18, 1.7.25, 1.8.17.
Conditions (all must be true for the bug to be hit):
- The application must use Phoenix.Presence and either track presences under a key influenced by client input, or define a fetch/2 callback that can raise on a tracked key. (source: https://www.cve.org/CVERecord?id=CVE-2026-128361)
- Affects phoenix 1.2.0 up to the fixed releases 1.5.16, 1.6.18, 1.7.25 and 1.8.17, depending on series. (source: https://cna.erlef.org/cves/CVE-2026-128361.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Validate every presence key before passing it to track/3,4, untrack/2,3 or update/3,4, so that only strings reach the tracker. (source: https://www.cve.org/CVERecord?id=CVE-2026-128361)
CISA KEV: CVE-2026-128361 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128361 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Hex): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/phoenixframework/phoenix/security/advisories/GHSA-pvfx-rx4x-phrr
- https://github.com/phoenixframework/phoenix/commit/39c1c6bfd0c817f1223c121f61c60a25f66b76cb
- https://github.com/phoenixframework/phoenix/commit/6609595fb3e37f545c4ac636a369f14b0084bc3d
- https://github.com/phoenixframework/phoenix/commit/81bc0278c7a4e6204f7e2e0a3b3200e9f1ee5a4b
- https://github.com/phoenixframework/phoenix/commit/edb702804aeab3a29543668a8be8ea61291c4b75
- https://cna.erlef.org/cves/CVE-2026-128361.html
- https://osv.dev/vulnerability/EEF-CVE-2026-128361
- https://github.com/phoenixframework/phoenix/commit/44e7618370629df93711cd6169789fd0d8f3678e
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128361
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128361"}.Affected versions
- phoenixFrom 1.2.0 · fixed in 1.5.16; From 1.6.0-rc.0 · fixed in 1.6.18; From 1.7.0-rc.0 · fixed in 1.7.25; From 1.8.0-rc.0 · fixed in 1.8.17
- phoenixframework/phoenixVersion range not reported
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects Hex packages
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 40 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 10
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · phoenixframework/phoenix · Advisory GHSA-pvfx-rx4x-phrr |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-128361 |
| Record | NVD · CVE-2026-128361 |
| Other links 7 | |
| Patch | GitHub · phoenixframework/phoenix · Commit 39c1c6bf |
| Patch | GitHub · phoenixframework/phoenix · Commit 6609595f |
| Patch | GitHub · phoenixframework/phoenix · Commit 81bc0278 |
| Patch | GitHub · phoenixframework/phoenix · Commit edb70280 |
| Repository | GitHub · phoenixframework/phoenix · Commit 44e76183 |
| Link | cna.erlef.org · cves/CVE-2026-128361.html |
| Link | osv.dev · vulnerability/EEF-CVE-2026-128361 |
Questions about CVE-2026-128361
Is CVE-2026-128361 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A single channel join can crash the Presence tracker shard when a presence key is not sanitized, which kills tracked channel and LiveView processes and wipes presence state. Repeated joins can take down the application supervisor, causing a denial of service.
Source: cve.org, cna.erlef.org, github.com
Which versions are affected by CVE-2026-128361?
phoenix (Hex): 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; from 1.8.0-rc.0 before 1.8.17.
Source: cve.now feed data
Am I affected, and how do I check?
The issue affects phoenix from 1.2.0 before the fixed releases 1.5.16, 1.6.18, 1.7.25 and 1.8.17, depending on series. It only applies when the application uses Phoenix.Presence and either tracks presences under a key influenced by client input or defines a fetch/2 callback that can raise on a tracked key. To check, look at the phoenix version in your mix.lock or deps and whether your code uses Phoenix.Presence.
Source: cve.org, cna.erlef.org, github.com
How do I fix CVE-2026-128361?
Upgrade to the fixed release for your series: 1.5.16, 1.6.18, 1.7.25 or 1.8.17. If you cannot upgrade yet, validate every presence key before passing it to track/3,4, untrack/2,3 or update/3,4 so that only strings reach the tracker.
Source: cve.org, cna.erlef.org, github.com
Related
- CVE-2026-56811Phoenix transports do not limit channel joins per connection, enabling process-exhaustion denial of service
- CVE-2026-32689Long-poll NDJSON body splitting causes unbounded memory allocation in Phoenix
- CVE-2026-129344Client-selected V1 serializer crashes shared broadcast dispatch on binary payloads
- CVE-2022-42975socket/transport.ex in Phoenix before 1.6.14 mishandles check_origin wildcarding.
- CVE-2026-56812Phoenix JavaScript presence client crashes on presence keys colliding with Object.prototype members in Presence.syncState/syncDiff
- CVE-2017-1000163The Phoenix Framework versions 1.0.0 through 1.0.4, 1.1.0 through 1.1.6, 1.2.0, 1.2.2 and 1.3.0-rc.0 are vulnerable to unvalidated URL…
No corrections so far. Something wrong on this page? Report an error.