7.5

CVE-2026-56812: Phoenix JavaScript presence client crashes on presence keys colliding with Object.prototype members in Presence.syncState/syncDiff

Modified
AliasesEEF-CVE-2026-56812GHSA-63mc-hw7g-86rr
Published 07-07-2026Last modified 24-09-2026

Vulnerability summary

CVE-2026-56812 is a high (CVSS 7.5) vulnerability in phoenixframework phoenix. EPSS estimates a 0.80% chance of exploitation in the next 30 days, higher than 57.3% of scored vulnerabilities. 1 public exploit is recorded.

Priority
Routine

Not severe (CVSS 6.3, network access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
7.5/10
010
High · v3.1 (NVD)
EPSS score
0.80%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits1github

Timeline

  1. 07-07-2026
    PublishedVulnerability first disclosed.
  2. 24-09-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

4 scores · 3 sources · 2 versions

EPSS trend

Probability

0.80%

Chance of exploitation in the next 30 days

Percentile

57%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.80% on 21-10-2026

21-10-202620-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

1 found
  • githubUnverified

    Phoenix

    Maturity: poc

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Hex1 product
  • phoenix≥ 1.2.0-rc.0, < 1.5.15 | ≥ 1.6.0-rc.0, < 1.6.17 | ≥ 1.7.0-rc.0, < 1.7.24 | ≥ 1.8.0-rc.0, < 1.8.9
Npm1 product
  • phoenix≥ 1.2.0-rc.0, < 1.5.15 | ≥ 1.6.0-rc.0, < 1.6.17 | ≥ 1.7.0-rc.0, < 1.7.24 | ≥ 1.8.0-rc.0, < 1.8.9
Phoenixframework1 product
  • phoenix≥ 1.2.0-rc.0, < 1.5.15 | ≥ 1.6.0-rc.0, < 1.6.17 | ≥ 1.7.0-rc.0, < 1.7.24 | ≥ 1.8.0-rc.0, < 1.8.9 | ≥ 2270aaf21bd02c6a6a1022820564efb605a97655 (No fix recorded) | ≥ 1.2.0, < 1.5.15 | ≥ 1.6.0, < 1.6.17 | ≥ 1.7.0, < 1.7.24 | ≥ 1.8.0, < 1.8.9

3 vendors · 3 products

References

12 links
Show all 12 references