CVE-2026-62247: CWE-863: Incorrect Authorization in supabase realtime
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.
AI Analysis
Technical Summary
CVE-2026-62247 is an incorrect authorization vulnerability in Supabase Realtime before version 2.111.2. The flaw arises because the realtime authorization mechanism does not correctly enforce the presence.read row-level security policy when a client is allowed presence.write but explicitly denied presence.read on private channels. As a result, such clients can receive presence_diff messages containing presence metadata of other members, including application-defined data like location, online status, roster, viewing, or typing information. This issue does not impact postgres_changes row data and only affects deployments with differential presence visibility policies. The vulnerability is resolved in version 2.111.2.
Potential Impact
An attacker or unauthorized client with presence.write permission but denied presence.read permission on private channels can access sensitive presence metadata of other users, potentially exposing private information such as location or online status. There is no impact on data integrity or availability, and postgres_changes data remains unaffected.
Mitigation Recommendations
Upgrade Supabase Realtime to version 2.111.2 or later where this authorization issue is fixed. No other mitigations are indicated by the vendor advisory.
CVE-2026-62247: CWE-863: Incorrect Authorization in supabase realtime
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 v3.1
Score 6.5medium
Affected software
supabase
realtime
pkg:github/supabase/realtimeRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-62247 is an incorrect authorization vulnerability in Supabase Realtime before version 2.111.2. The flaw arises because the realtime authorization mechanism does not correctly enforce the presence.read row-level security policy when a client is allowed presence.write but explicitly denied presence.read on private channels. As a result, such clients can receive presence_diff messages containing presence metadata of other members, including application-defined data like location, online status, roster, viewing, or typing information. This issue does not impact postgres_changes row data and only affects deployments with differential presence visibility policies. The vulnerability is resolved in version 2.111.2.
Potential Impact
An attacker or unauthorized client with presence.write permission but denied presence.read permission on private channels can access sensitive presence metadata of other users, potentially exposing private information such as location or online status. There is no impact on data integrity or availability, and postgres_changes data remains unaffected.
Mitigation Recommendations
Upgrade Supabase Realtime to version 2.111.2 or later where this authorization issue is fixed. No other mitigations are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-13T17:09:57.573Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ab1863b55bf5e2cf55cd548
Added to database: 09/21/2026, 19:32:11 UTC
Last enriched: 09/21/2026, 19:46:36 UTC
Last updated: 09/21/2026, 22:11:59 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.