Skip to content
Noroxi
NVD / CVE Program· CNA EEF

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

MediumCVSS 6.3 · v4.0—No exploit Fix available

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

Report tools

JSON

Action score

25

Monitor

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.

Follow CVE-2026-56812

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
phoenixframeworkphoenix

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

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Hexphoenixfrom 1.2.0-rc.0 · before 1.5.151.5.15
Hexphoenixfrom 1.6.0-rc.0 · before 1.6.171.6.17
Hexphoenixfrom 1.7.0-rc.0 · before 1.7.241.7.24
Hexphoenixfrom 1.8.0-rc.0 · before 1.8.91.8.9
npmphoenixfrom 1.2.0-rc.0 · before 1.5.151.5.15
npmphoenixfrom 1.6.0-rc.0 · before 1.6.171.6.17
npmphoenixfrom 1.7.0-rc.0 · before 1.7.241.7.24
npmphoenixfrom 1.8.0-rc.0 · before 1.8.91.8.9

Other highest-scoring records for the same primary product.

  • CVE-2026-56811Phoenix transports do not limit channel joins per connection, enabling process-exhaustion denial of service
    34Monitor
  • CVE-2026-32689Long-poll NDJSON body splitting causes unbounded memory allocation in Phoenix
    34Monitor
  • 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 / packageFixed versionSource
phoenixframework phoenix1.5.15Vendor (CNA)
phoenixframework phoenix1.6.17Vendor (CNA)
phoenixframework phoenix1.7.24Vendor (CNA)
phoenixframework phoenix1.8.9Vendor (CNA)
phoenixframework phoenix7f7b971c1ea0994e3fbd1c11ddb05e780bd38ad8Vendor (CNA)
phoenixframework phoenix89a1c4be161e436241e12b2378a719904b9bd96fVendor (CNA)
phoenixframework phoenixb90b22521465ece00eb5a19d5aa2b9465b209c85Vendor (CNA)
phoenixframework phoenixbeffc4da1e787e572121f68902c63daf4fe7d9c2Vendor (CNA)
Hex:phoenix1.5.15Package registry (OSV)
Hex:phoenix1.6.17Package registry (OSV)
Hex:phoenix1.7.24Package registry (OSV)
Hex:phoenix1.8.9Package registry (OSV)
npm:phoenix1.5.15Package registry (OSV)
npm:phoenix1.6.17Package registry (OSV)
npm:phoenix1.7.24Package registry (OSV)
npm:phoenix1.8.9Package 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.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

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

CVSS 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.

References

All records