CVE-2026-56812: Phoenix JavaScript presence client crashes on presence keys colliding with Object.prototype members in Presence.syncState/syncDiff
Noroxi assessment
Priority: Monitor (action score 25/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.79% (FIRST EPSS); higher than 57% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: phoenixframework phoenix 1.5.15, 1.6.17, 1.7.24.
Low priority for now. Upgrade to phoenixframework phoenix 1.5.15, 1.6.17, 1.7.24 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 7, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.7% · 57th percentile
- CWE
- CWE-754
Report tools
Action score
25
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · EEF
- 6.3
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| phoenixframework | phoenix | cpe:2.3:a:phoenixframework:phoenix |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (EEF). Independent of NVD's CPE analysis and usually ahead of it.
phoenixframework phoenix
- 1.2.0-rc.0 and later · before 1.5.15affected · semver
- 1.6.0-rc.0 and later · before 1.6.17affected · semver
- 1.7.0-rc.0 and later · before 1.7.24affected · semver
- 1.8.0-rc.0 and later · before 1.8.9affected · semver
- 1.2.0-rc.0 and later · before 1.5.15affected · semver
- 1.6.0-rc.0 and later · before 1.6.17affected · semver
- 1.7.0-rc.0 and later · before 1.7.24affected · semver
- 1.8.0-rc.0 and later · before 1.8.9affected · semver
- 2270aaf21bd02c6a6a1022820564efb605a97655 and lateraffected · gitfixed in 7f7b971c1ea0994e3fbd1c11ddb05e780bd38ad8, 89a1c4be161e436241e12b2378a719904b9bd96f, b90b22521465ece00eb5a19d5aa2b9465b209c85, beffc4da1e787e572121f68902c63daf4fe7d9c2
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixframework phoenix1.2.0 and later · before 1.5.15
- phoenixframework phoenix1.6.0 and later · before 1.6.17
- phoenixframework phoenix1.7.0 and later · before 1.7.24
- phoenixframework phoenix1.8.0 and later · before 1.8.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Hex | phoenix | from 1.2.0-rc.0 · before 1.5.15 | 1.5.15 |
| Hex | phoenix | from 1.6.0-rc.0 · before 1.6.17 | 1.6.17 |
| Hex | phoenix | from 1.7.0-rc.0 · before 1.7.24 | 1.7.24 |
| Hex | phoenix | from 1.8.0-rc.0 · before 1.8.9 | 1.8.9 |
| npm | phoenix | from 1.2.0-rc.0 · before 1.5.15 | 1.5.15 |
| npm | phoenix | from 1.6.0-rc.0 · before 1.6.17 | 1.6.17 |
| npm | phoenix | from 1.7.0-rc.0 · before 1.7.24 | 1.7.24 |
| npm | phoenix | from 1.8.0-rc.0 · before 1.8.9 | 1.8.9 |
Same product
phoenixframework: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-56811Phoenix transports do not limit channel joins per connection, enabling process-exhaustion denial of service34Monitor
- CVE-2026-32689Long-poll NDJSON body splitting causes unbounded memory allocation in Phoenix34Monitor
- CVE-2022-42975socket/transport.ex in Phoenix before 1.6.14 mishandles check_origin wildcarding.30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2017-1000163Nov 17, 2017 · The Phoenix Framework versions 1.0.0 through 1.0.4, 1.1.0 through 1.1.6, 1.2.0, 1.2.2 and 1.3.0-rc.0 are vulnerable to unvalidated URL…25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| phoenixframework phoenix | 1.5.15 | Vendor (CNA) |
| phoenixframework phoenix | 1.6.17 | Vendor (CNA) |
| phoenixframework phoenix | 1.7.24 | Vendor (CNA) |
| phoenixframework phoenix | 1.8.9 | Vendor (CNA) |
| phoenixframework phoenix | 7f7b971c1ea0994e3fbd1c11ddb05e780bd38ad8 | Vendor (CNA) |
| phoenixframework phoenix | 89a1c4be161e436241e12b2378a719904b9bd96f | Vendor (CNA) |
| phoenixframework phoenix | b90b22521465ece00eb5a19d5aa2b9465b209c85 | Vendor (CNA) |
| phoenixframework phoenix | beffc4da1e787e572121f68902c63daf4fe7d9c2 | Vendor (CNA) |
| Hex:phoenix | 1.5.15 | Package registry (OSV) |
| Hex:phoenix | 1.6.17 | Package registry (OSV) |
| Hex:phoenix | 1.7.24 | Package registry (OSV) |
| Hex:phoenix | 1.8.9 | Package registry (OSV) |
| npm:phoenix | 1.5.15 | Package registry (OSV) |
| npm:phoenix | 1.6.17 | Package registry (OSV) |
| npm:phoenix | 1.7.24 | Package registry (OSV) |
| npm:phoenix | 1.8.9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Peter Ullrichfinder
- Steffen Deuschremediation developer
- José Valimanalyst
- Jonatan Männchen / EEFanalyst
Not on record for this CVE: EPSS history · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-754 · Improper Check for Unusual or Exceptional ConditionsCVSS vector
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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- github.com/phoenixframework/phoenix/commit/2270aaf21bd02c6a6a1022820564efb605a97655
- github.com/phoenixframework/phoenix/commit/7f7b971c1ea0994e3fbd1c11ddb05e780bd38ad8
- github.com/phoenixframework/phoenix/commit/89a1c4be161e436241e12b2378a719904b9bd96f
- github.com/phoenixframework/phoenix/commit/b90b22521465ece00eb5a19d5aa2b9465b209c85
- github.com/phoenixframework/phoenix/commit/beffc4da1e787e572121f68902c63daf4fe7d9c2
- osv.dev/vulnerability/EEF-CVE-2026-56812
Vendor advisories and official records. Exploit/PoC links are deliberately left out.