CVE-2026-54238
Supabase Realtime provides Broadcast, Presence, and Postgres …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/supabase/realtime/commit/ac229d7eff2798b12b994e07bdd64f5e9b56374a
- github.com/supabase/realtime/pull/1934
- github.com/supabase/realtime/releases/tag/v2.103.1
- github.com/supabase/realtime/security/advisories/GHSA-hg9h-6mhq-6c2v
- nvd.nist.gov/vuln/detail/CVE-2026-54238
- cve.org/CVERecord?id=CVE-2026-54238
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.