Vulnerability EEF-CVE-2026-56812

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
4 months ago
July 07, 2026 at 03:22 PM UTC
Phoenix JavaScript presence client crashes on presence keys colliding with Object.prototype members in Presence.syncState/syncDiff
1.2.0-rc.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8
1.2.0-rc.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8

Summary

Phoenix JavaScript presence client crashes on presence keys colliding with Object.prototype members in Presence.syncState/syncDiff

Details

Summary

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.

Workarounds

Reject or sanitize presence keys that collide with JavaScript Object.prototype member names (for example __proto__, constructor, prototype, toString, hasOwnProperty) before calling Phoenix.Presence.track, or namespace every presence key with a fixed prefix so that no key can equal a prototype member name. Alternatively, derive presence keys from server-controlled, validated values instead of raw user input.

Configurations

The application must use Phoenix.Presence (or otherwise drive the Phoenix JavaScript presence client) and track presences under keys that are influenced by untrusted client input, for example a username or id chosen by the connecting user. Applications that derive presence keys exclusively from server-controlled, validated values are not affected.

Related Vulnerabilities

Other vulnerabilities affecting the same packages

Unknown
1 day ago
Unsanitized presence key crashes Presence tracker
1.2.0 - 1.5.15 and 1.6.0-rc.0 - 1.6.17 and 1.7.0-rc.0 - 1.7.24 and 1.8.0-rc.0 - 1.8.16 EEF-CVE-2026-128361
1.2.0 - 1.5.15 and 1.6.0-rc.0 - 1.6.17 and 1.7.0-rc.0 - 1.7.24 and 1.8.0-rc.0 - 1.8.16 EEF-CVE-2026-128361
Unknown
1 day ago
Client-selected V1 serializer crashes shared broadcast dispatch on binary payloads
1.5.7 - 1.5.15 and 1.6.0-rc.0 - 1.6.17 and 1.7.0-rc.0 - 1.7.24 and 1.8.0-rc.0 - 1.8.16 EEF-CVE-2026-129344
1.5.7 - 1.5.15 and 1.6.0-rc.0 - 1.6.17 and 1.7.0-rc.0 - 1.7.24 and 1.8.0-rc.0 - 1.8.16 EEF-CVE-2026-129344
High Risk
2 months ago
Phoenix: Unbounded channel joins per transport enables DoS over few connections
0.11.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 GHSA-6983-jfq8-485w
0.11.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 GHSA-6983-jfq8-485w
Medium Risk
2 months ago
Phoenix: Presence keys colliding with `Object.prototype` members break existence checks
1.2.0-rc.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 GHSA-63mc-hw7g-86rr
1.2.0-rc.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 GHSA-63mc-hw7g-86rr
Medium Risk
2 months ago
Phoenix: Presence keys colliding with `Object.prototype` members break existence checks
1.2.0-rc.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 GHSA-63mc-hw7g-86rr
1.2.0-rc.0 - 1.5.14 and 1.6.0-rc.0 - 1.6.16 and 1.7.0-rc.0 - 1.7.23 and 1.8.0-rc.0 - 1.8.8 GHSA-63mc-hw7g-86rr
View all vulnerabilities for these packages

Impacted packages

Timeline

Published
4 months ago
July 07, 2026 at 03:22 PM UTC
Fixed (1.8.9)
4 months ago
July 07, 2026 at 12:22 PM UTC
Fixed (1.8.9)
4 months ago
July 07, 2026 at 12:23 PM UTC
Fixed (1.7.24)
4 months ago
July 07, 2026 at 12:25 PM UTC
Fixed (1.7.24)
4 months ago
July 07, 2026 at 12:27 PM UTC
Fixed (1.6.17)
4 months ago
July 07, 2026 at 12:53 PM UTC
Fixed (1.5.15)
4 months ago
July 07, 2026 at 12:56 PM UTC
Fixed (1.6.17)
4 months ago
July 07, 2026 at 12:58 PM UTC
Fixed (1.5.15)
4 months ago
July 07, 2026 at 12:59 PM UTC
Last Modified
2 days ago
November 20, 2026 at 06:01 AM UTC