CVE-2026-128361
Received Received - Intake

Denial of Service in Phoenix Framework via Presence Key

Vulnerability report for CVE-2026-128361, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-21

Last updated on: 2026-11-21

Assigner: EEF

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-21
Last Modified
2026-11-21
Generated
2026-11-21
AI Q&A
2026-11-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 12 associated CPEs
Vendor Product Version / Range
phoenixframework phoenix From 1.2.0 (inc) to 1.5.16 (exc)
phoenixframework phoenix From 1.6.0 (inc) to 1.6.18 (exc)
phoenixframework phoenix From 1.7.0 (inc) to 1.7.25 (exc)
phoenixframework phoenix From 1.8.0 (inc) to 1.8.17 (exc)
phoenixframework phoenix to 1.5.16 (exc)
phoenixframework phoenix to 1.6.18 (exc)
phoenixframework phoenix to 1.7.25 (exc)
phoenixframework phoenix to 1.8.17 (exc)
phoenixframework phoenix 1.5.16
phoenixframework phoenix 1.6.18
phoenixframework phoenix 1.7.25
phoenixframework phoenix 1.8.17

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an Improper Input Validation vulnerability in the Phoenix framework's Presence tracker. An attacker who can join a channel can cause a denial of service by providing a non-string presence key, such as a JSON object. This triggers a Protocol.UndefinedError when the key is converted to a string later in the process. The error crashes channels or entire Presence shards, taking down linked processes and erasing presence state. Repeated exploitation can crash the application supervisor.

Detection Guidance

To detect this vulnerability, monitor for crashes in Phoenix Presence tracker processes or channels. Check logs for Protocol.UndefinedError exceptions during presence key processing. In affected versions, non-string keys like JSON objects in join payloads trigger crashes. Use system monitoring tools to watch for abnormal termination of Phoenix processes or LiveView channels.

Impact Analysis

If you use a vulnerable Phoenix version, an attacker could join a channel and crash your application by sending a non-string presence key. This causes downtime for all channels or LiveViews on the affected Presence shard. In severe cases, repeated attacks may crash your entire application, leading to loss of service and potential data loss.

Compliance Impact

This vulnerability could impact compliance by causing service disruptions or data loss, which may violate availability requirements in GDPR and HIPAA. Downtime or crashes could lead to unauthorized access or data breaches if presence state is lost or corrupted during an attack.

Mitigation Strategies
  • Upgrade Phoenix framework to patched versions: 1.5.16, 1.6.18, 1.7.25, or 1.8.17 or later.
  • Validate all presence keys before using them in Presence.track/2 or Presence.track/3 functions to ensure they are strings.
  • Review channel join payloads to ensure no non-string keys like JSON objects are being passed as presence keys.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-128361. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...