CVE-2026-62247
Supabase Realtime provides Broadcast, Presence, and Postgres …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/supabase/realtime/commit/c039bca9b57c2e554a67fdf462970b54641d82eb
- github.com/supabase/realtime/pull/1969
- github.com/supabase/realtime/releases/tag/v2.111.2
- github.com/supabase/realtime/security/advisories/GHSA-rcr8-2525-4r7p
- nvd.nist.gov/vuln/detail/CVE-2026-62247
- cve.org/CVERecord?id=CVE-2026-62247
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.