Vulnerability Description
Supabase Realtime provides Broadcast, Presence, and Postgres Changes via WebSockets. Prior to 2.111.2, Realtime authorization does not correctly honor the per-extension presence.read row-level security policy when a private-channel client is allowed presence.write but explicitly denied presence.read. Under that differential policy, the client can receive presence_diff messages containing other members' presence metadata, including application-defined location, online-status, roster, viewing, or typing information. Deployments with uniform presence visibility have no differential, and postgres_changes row data is unaffected. This issue is fixed in version 2.111.2.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/supabase/realtime/commit/c039bca9b57c2e554a67fdf462970b54641d
- https://github.com/supabase/realtime/pull/1969
- https://github.com/supabase/realtime/releases/tag/v2.111.2
- https://github.com/supabase/realtime/security/advisories/GHSA-rcr8-2525-4r7p
FAQ
What is CVE-2026-62247?
CVE-2026-62247 is a vulnerability with a CVSS score of 6.5 (MEDIUM). Supabase Realtime provides Broadcast, Presence, and Postgres Changes via WebSockets. Prior to 2.111.2, Realtime authorization does not correctly honor the per-extension presence.read row-level securit...
How severe is CVE-2026-62247?
CVE-2026-62247 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-62247?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.