rewindex

RewindexCVEsSupabase

CVE-2026-54238: Supabase Realtime: Expired JWTs with string exp are accepted by REST broadcast authorization

Low · CVSS 3.1 (CVSS 3.1)EPSS 0.21%, 11th percentilePublished Updated Assigner: GitHub_M

Description

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.

Vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N · CWE-613

Tracked companies

Supabase

Mapped from the CVE’s affected-product data, NVD CPE matches, vendor advisories or package feeds. A mapping means the vendor’s software is named, not that its hosted service was exposed.

Status incidents that name it

No tracked status incident names this CVE.

Affected vendors and products

supabase: realtime

References

All CVEsMarkdownJSON