Approved changes feed: RSS · Atom

cpe:2.3:a:supabase:realtime:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorSupabase (4d4a37e3-8b8c-55aa-a7b8-1815951ff558)
ProductRealtime (4c057438-299c-5494-b67c-8cb0e1bc597c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-54238 vulnerable 2026-11-03 10:16:55.518487 Supabase Realtime: Expired JWTs with string exp are accepted by REST broadcast authorization
LOW (3.1)
Supabase Realtime provides Broadcast, Presence, and Postgres Changes via WebSockets. Prior to version 2.103.1, the REST broadcast endpoints accept an expired JWT when the exp claim is encoded as a JSON string instead of a JSON number. The same route rejects an expired integer exp token signed with the same tenant secret. The accepted request returns 202 and emits the broadcast to subscribers. This could allow an unauthenticated attacker can broadcast realtime messages to subscribers. The attack can be performed via the Internet/only from within the supabase project. The impact of broadcasting messages to subscribers is application specific. This issue has been patched in version 2.103.1.
Published: 2026-10-22T17:22:50.862Z
Updated: 2026-10-30T15:11:34.608Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-62247 vulnerable 2026-10-13 12:28:41.428555 Supabase Realtime: Incorrect Authorization
MEDIUM (6.5)
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.
Published: 2026-09-21T19:04:58.743Z
Updated: 2026-09-22T15:40:12.145Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.