No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 23 Sep 2026 03:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 22 Sep 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Supabase
Supabase realtime |
|
| Vendors & Products |
Supabase
Supabase realtime |
Mon, 21 Sep 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Supabase Realtime: Incorrect Authorization | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-22T15:40:12.145Z
Reserved: 2026-07-13T17:09:57.573Z
Link: CVE-2026-62247
Updated: 2026-09-22T14:12:27.403Z
Status : Received
Published: 2026-09-21T20:17:27.470
Modified: 2026-09-22T16:17:50.457
Link: CVE-2026-62247
No data.
OpenCVE Enrichment
Updated: 2026-09-22T19:25:08Z