CVE-2026-56812

Description

Improper Check for Unusual or Exceptional Conditions vulnerability in phoenixframework phoenix (Presence JavaScript client) allows an attacker with ordinary channel access to cause a persistent client-side denial of service against every viewer of a presence channel topic. This vulnerability is associated with program files assets/js/phoenix/presence.js and program routines Presence.syncState and Presence.syncDiff. The Phoenix JavaScript presence client checks whether a presence already exists with a bare truthiness test (state[key]) instead of an own-property check. Presence keys can be attacker-controlled, because applications track presences under a username or id supplied by the client. A user who joins a channel choosing a key that is an Object.prototype member name (__proto__, constructor, toString, hasOwnProperty, and similar) makes that lookup return JavaScript's built-in Object.prototype instead of undefined. Because the prototype is truthy, the code treats it as an existing presence and reads .metas.map(...) off it, which throws an uncaught TypeError. The exception propagates out of the presence message handler, so the local state is never updated and onSync() never fires. Because the malicious key is tracked on the server, it is re-pushed on every presence update and keeps re-throwing, so presence sync stays broken for every viewer of that channel topic until the attacker leaves. Both syncState and syncDiff use the same unsafe existence-check pattern. The impact is limited to the affected topic and is a read-time confusion of the prototype object, not a mutation of Object.prototype (it is not prototype pollution). This issue affects phoenix: from 1.2.0-rc.0 before 1.5.15, from 1.6.0-rc.0 before 1.6.17, from 1.7.0-rc.0 before 1.7.24, and from 1.8.0-rc.0 before 1.8.9; phoenix: from 1.2.0-rc.0 before 1.5.15, from 1.6.0-rc.0 before 1.6.17, from 1.7.0-rc.0 before 1.7.24, and from 1.8.0-rc.0 before 1.8.9.

Severity
HIGH
CVSS v3
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H · source nvd
CVSS v4
6.3
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · source cna
Exploit chance (EPSS)
0.796%
chance of exploitation in the next 30 days
higher than 57.1% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 1
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableno
Technical impactpartial
Scored2026-07-07

Timeline

  1. 2026-07-07Published by the CNA15:22 UTC
  2. 2026-07-07CISA SSVC decision recordedsame day
  3. 2026-09-03GitHub advisory published (GHSA-63mc-hw7g-86rr)58 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-63mc-hw7g-86rr, affected packages:

PackageVulnerable versionsFixed in
npm phoenixfrom 1.2.0-rc.0 before 1.5.151.5.15
npm phoenixfrom 1.6.0-rc.0 before 1.6.171.6.17
npm phoenixfrom 1.7.0-rc.0 before 1.7.241.7.24
npm phoenixfrom 1.8.0-rc.0 before 1.8.91.8.9

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
phoenixframework phoenixfrom 1.2.0 before 1.5.15fixed in 1.5.15from 1.2.0-rc.0 before 1.5.15fixed in 1.5.15from 1.6.0 before 1.6.17fixed in 1.6.17from 1.6.0-rc.0 before 1.6.17fixed in 1.6.17from 1.7.0 before 1.7.24fixed in 1.7.24(+3 more)1.5.151.5.151.6.171.6.171.7.24

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources