cve.bz

CVE-2026-56812 phoenixframework phoenix

6.3 mediumExploit referenceEPSS 0.8%Fix available

Medium (6.3) in phoenixframework phoenix. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in phoenix 1.5.15, 1.6.17, 1.7.24.

On this page
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.

Severity

CVSS 4.0

6.3 medium
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

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 57th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-07-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-754 Improper Check for Unusual or Exceptional Conditions
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-56812 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-56812?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-56812?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-56812 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
phoenixframework phoenixfrom 1.2.0-rc.0 before 1.5.15
phoenixframework phoenixfrom 1.6.0-rc.0 before 1.6.17
phoenixframework phoenixfrom 1.7.0-rc.0 before 1.7.24
phoenixframework phoenixfrom 1.8.0-rc.0 before 1.8.9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-56812Hexphoenix>=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
1.5.15, 1.6.17, 1.7.24, 1.8.9
EEF-CVE-2026-56812npmphoenix>=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
1.5.15, 1.6.17, 1.7.24, 1.8.9
EEF-CVE-2026-56812v1.5.13, v1.6.16, v1.7.23, v1.8.8, v1.8.7 and 80 moreno fix published
GHSA-63mc-hw7g-86rrHexphoenix>=1.2.0-rc.0 <1.5.151.5.15
GHSA-63mc-hw7g-86rrHexphoenix>=1.6.0-rc.0 <1.6.171.6.17
GHSA-63mc-hw7g-86rrHexphoenix>=1.7.0-rc.0 <1.7.241.7.24
GHSA-63mc-hw7g-86rrHexphoenix>=1.8.0-rc.0 <1.8.91.8.9
GHSA-63mc-hw7g-86rrnpmphoenix>=1.2.0-rc.0 <1.5.151.5.15
GHSA-63mc-hw7g-86rrnpmphoenix>=1.6.0-rc.0 <1.6.171.6.17
GHSA-63mc-hw7g-86rrnpmphoenix>=1.7.0-rc.0 <1.7.241.7.24
GHSA-63mc-hw7g-86rrnpmphoenix>=1.8.0-rc.0 <1.8.91.8.9

References

Check your stackJSON