CVE-2026-62247 Supabase Realtime: Incorrect Authorization
Attackers with write but no read permissions can view other users' presence metadata in private channels.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-62247?
CVE-2026-62247 is a medium-severity missing authorization vulnerability in supabase realtime, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-863
Which versions are affected by CVE-2026-62247?
How do I fix CVE-2026-62247?
No fix has been published for CVE-2026-62247 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-62247 being exploited?
There is no known exploitation of CVE-2026-62247 in the wild and no public exploit code.
Sources
Also known as GHSA-rcr8-2525-4r7p.