Chatify before 1.6.4 Pusher Authorization Bypass via /chat/auth Endpoint
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 1.6.4
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Chatify installation using the Pusher channel authorization endpoint before 1.6.4
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.6.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
Chatify, a chat software package, is affected by an authorization flaw in its real-time messaging channel authentication. A logged-in user can gain access to other users' private conversations, including messages and attachments as they are sent.
Read the original description
Chatify before 1.6.4 contains an authorization bypass vulnerability in the Pusher channel authorization endpoint that allows authenticated users to subscribe to other users' private channels by supplying arbitrary channel names. Attackers can request a signature for private-chatify.<victim id> via POST /chat/auth to receive the victim's incoming private messages and attachments in real time.
What to do
Check whether your setup matches what the bug needs.
Chatify installation using the Pusher channel authorization endpoint before 1.6.4Upgrade to a fixed version: 1.6.4.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- munafio Chatify
fixed in 1.6.4
Evidence 6
- Patch
- Report
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120425
What does this mean?
The Pusher channel authorization endpoint in Chatify signs requests for private channels without properly restricting them to the signed-in user's own channel. This lets a user subscribe to channels beyond their own.Source: github.com, github.com
Am I affected, and how do I check?
Chatify installations before 1.6.4 that use the Pusher channel authorization endpoint are affected. To check, look at the Chatify version in your project's composer.lock or vendor files, and check whether your setup uses Pusher for chat channels.Source: github.com, github.com
What should I do about it?
Upgrade Chatify to version 1.6.4 or later, which restricts Pusher channel authorization to the authenticated user's own channel.Source: github.com, github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data