Threat database

CVE-2026-54238 is a vulnerability in Supabase Realtime prior to version 2.103.1 where expired JWT tokens with the exp claim encoded as a JSON string are incorrectly accepted by REST broadcast endpoints. This allows an unauthenticated attacker to broadcast realtime messages to subscribers. The issue is patched in version 2.103.1.

CVE-2026-62247 is an authorization vulnerability in Supabase Realtime prior to version 2.111.2. The issue arises when a private-channel client is allowed presence.write permission but denied presence.read permission under a differential row-level security policy. In this scenario, the client can receive presence_diff messages revealing other members' presence metadata such as location, online status, and typing information. Deployments without differential presence visibility or those only using postgres_changes data are not affected. The vulnerability is fixed in version 2.111.2.

Supabase Auth is a JWT based API for managing users and issuing JWT tokens. Prior to 2.185.0, a vulnerability has been identified that allows an attacker to issue sessions for arbitrary users using specially crafted ID tokens when the Apple or Azure providers are enabled. The attacker issues a valid, asymmetrically signed ID token from their issuer for each victim email address, which then is sent to the Supabase Auth token endpoint using the ID token flow. If the ID token is OIDC compliant, the Auth server would validate it against the attacker-controlled issuer and link the existing OIDC identity (Apple or Azure) of the victim to an additional OIDC identity based on the ID token contents. The Auth server would then issue a valid user session (access and refresh tokens) at the AAL1 level to the attacker. This vulnerability is fixed in 2.185.0.

EPSS 0.2%Vulnerabilitysupabase#cwe-290United States+9

auth-js is an isomorphic Javascript library for Supabase Auth. Prior to version 2.70.0, the library functions getUserById, deleteUser, updateUserById, listFactors and deleteFactor did not require the user supplied values to be valid UUIDs. This could lead to a URL path traversal, resulting in the wrong API function being called. Implementations that follow security best practice and validate user controlled inputs, such as the userId are not affected by this. This issue has been patched in version 2.70.0.

EPSS 0.9%Vulnerabilitysupabase#cwe-287#cwe-22Germany+5