Skip to main content
VulnerabilityPublished Updated

CVE-2026-56812: phoenixframework phoenix · Unchecked Error Condition

Affects phoenixframework phoenixSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium · fixed in 1.8.9 : update phoenixframework phoenix when convenient.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.8.9, 1.7.24, 1.6.17 +1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade phoenixframework phoenix to 1.8.9, 1.7.24, 1.6.17 or 1.5.15.

Affected software

ProductAffectedFixed in
phoenixframeworkphoenixAffected
  • >=1.8.0-rc.0 <1.8.9
Fixed in
  • 1.8.9
phoenixframeworkphoenixAffected
  • >=1.7.0-rc.0 <1.7.24
Fixed in
  • 1.7.24
phoenixframeworkphoenixAffected
  • >=1.6.0-rc.0 <1.6.17
Fixed in
  • 1.6.17
phoenixframeworkphoenixAffected
  • >=1.2.0-rc.0 <1.5.15
Fixed in
  • 1.5.15
phoenixframeworkphoenixAffected
  • ≥ 2270aaf21bd02c6a6a1022820564efb605a97655, < 7f7b971c1ea0994e3fbd1c11ddb05e780bd38ad8
Fixed in–
Hexphoenixpkg:hex/phoenixOther threatsAffected
  • >=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
Fixed in
  • 1.5.15
  • 1.6.17
  • 1.7.24
  • 1.8.9

CPE configurations (1)

  • cpe:2.3:a:phoenixframework:phoenix:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, applications should avoid using untrusted user-supplied keys as presence identifiers or implement own-property checks to safely handle presence keys. Monitoring for unusual presence keys that match Object.prototype properties may help detect exploitation attempts.

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.

References

Community reviews

Loading reviews…