CVE-2026-56812Phoenix JavaScript presence client crashes on presence keys colliding with Object.prototype members in Presence.syncState/syncDiff
- 6.3MediumCVSS base score
- 0.80%Exploitation in 30 daysEPSS · top 43% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- YesPublic exploitsa reference or SSVC says so
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.
Public exploit
An exploit or proof of concept is public: anyone can try it against an unpatched system. A reference of the record is tagged as an exploit. CISA's SSVC rates its exploitation: a proof of concept is public.
Show the exploits1
References tagged exploit1 reference
- https://github.com/phoenixframework/phoenix/security/advisories/GHSA-63mc-hw7g-86rr (opens in a new tab)vendor-advisoryrelatedexploit
Timeline
ID reserved
By EEF
- 14 days later
· 14 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| EEFCNA (assigner) | 4.0 | Medium6.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 |
| NVDNVD · Modified | 4.0 | Medium6.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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
- EPSS (exploitation in 30 days)
- 0.80% · top 43% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: poc · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.3.
Affected products
- affected 1.2.0-rc.0 – < 1.5.15
- affected 1.6.0-rc.0 – < 1.6.17
- affected 1.7.0-rc.0 – < 1.7.24
- affected 1.8.0-rc.0 – < 1.8.9
- affected 1.2.0-rc.0 – < 1.5.15
- affected 1.6.0-rc.0 – < 1.6.17
- affected 1.7.0-rc.0 – < 1.7.24
- affected 1.8.0-rc.0 – < 1.8.9
- affected 2270aaf21bd02c6a6a1022820564efb605a97655 – < *
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- HexphoenixGHSA-63mc-hw7g-86rr (opens in a new tab)
- npmphoenixGHSA-63mc-hw7g-86rr (opens in a new tab)
What to do
Workaround: 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.
References
References8
- https://github.com/phoenixframework/phoenix/security/advisories/GHSA-63mc-hw7g-86rr (opens in a new tab)vendor-advisoryrelatedexploit
- EEF CNA record for CVE-2026-56812 (opens in a new tab)related
- OSV record EEF-CVE-2026-56812 (opens in a new tab)related
- Introducing commit 2270aaf in phoenixframework/phoenix (opens in a new tab)related
- Fix commit 7f7b971 in phoenixframework/phoenix (opens in a new tab)patch
- Fix commit 89a1c4b in phoenixframework/phoenix (opens in a new tab)patch
- Fix commit b90b225 in phoenixframework/phoenix (opens in a new tab)patch
- Fix commit beffc4d in phoenixframework/phoenix (opens in a new tab)patch
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-42050 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-63mc-hw7g-86rr (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-56812)Record last updated .