CVE-2026-54238

low

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.

References

https://github.com/supabase/realtime/security/advisories/GHSA-hg9h-6mhq-6c2v

https://github.com/supabase/realtime/releases/tag/v2.103.1

https://github.com/supabase/realtime/pull/1934

https://github.com/supabase/realtime/commit/ac229d7eff2798b12b994e07bdd64f5e9b56374a

https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-108263

Details

Source: Mitre, NVD

Published: 2026-10-22

Updated: 2026-10-22

Risk Information

CVSS v2

Base Score: 2.1

Vector: CVSS2#AV:N/AC:H/Au:S/C:N/I:P/A:N

Severity: Low

CVSS v3

Base Score: 3.1

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

Severity: Low