Supabase Realtime: Incorrect Authorization
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-863.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA realtime (supabase) Fixed in 2.111.2
Timeline
- 2026-10-02 Threatist record created from CVE-2026-62247
References
More supabase vulnerabilities
- TI-2024-16040 Supabase PostgreSQL v15.1 was discovered to contain a SQL injection vulnerability via the… CVSS 3.1CRITICAL 9.8
- TI-2026-24366 Supabase Auth has insecure Apple and Azure authentication with ID tokens CVSS 3.1MEDIUM 4.8
- TI-2025-30696 auth-js Vulnerable to Insecure Path Routing from Malformed User Input CVSS 4.0LOW 2.7
- TI-2026-79331 Expired JWTs accepted by Supabase Realtime REST broadcast endpoints CVSS 3.1LOW 3.1
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences