CVE-2026-62247
Received Received - Intake

Supabase Realtime Presence Data Exposure via WebSocket

Publication date: 2026-09-21

Last updated on: 2026-09-21

Assigner: GitHub, Inc.

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-21
Last Modified
2026-09-21
Generated
2026-09-22
AI Q&A
2026-09-21
EPSS Evaluated
N/A
NVD
CVE-2026-62247
EUVD
EUVD-2026-84066

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
supabase realtime to 2.111.2 (exc)
supabase realtime 2.111.2
supabase realtime From 2.112.2 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Supabase Realtime versions before 2.111.2. It involves incorrect authorization where presence.read permissions are not properly enforced. Users with presence.write access but explicitly denied presence.read could still receive presence_diff messages containing other members' metadata like location, online status, or typing information. The issue arises from improper permission checks in the authorization logic.

Detection Guidance

To detect this vulnerability, check the version of Supabase Realtime running on your system. If it is version 2.111.1 or earlier, the system is vulnerable. Use commands like 'npm list @supabase/realtime' or 'docker inspect <container> | grep RELEASE' to verify the installed version.

Impact Analysis

The vulnerability could lead to unauthorized access to sensitive presence metadata in private channels. Attackers with write-only access might view other users' live location, online status, roster, or typing indicators. This compromises confidentiality but does not affect data integrity or availability. Deployments with uniform presence visibility are unaffected.

Compliance Impact

This vulnerability could potentially affect compliance with GDPR and HIPAA by allowing unauthorized access to presence metadata such as live location, online status, or typing indicators. This unauthorized disclosure of personal or sensitive data may violate data protection requirements under these regulations.

Mitigation Strategies

Immediately update Supabase Realtime to version 2.111.2 or later. This can be done via package managers like npm ('npm update @supabase/realtime') or by pulling the latest Docker image. Verify the update was applied successfully.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-62247. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart