CVE-2026-31813: Supabase Auth has insecure Apple and Azure authentication with ID tokens
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-31813?
CVE-2026-31813 is considered a significant security vulnerability due to the potential for unauthorized access to user sessions.
How do I fix CVE-2026-31813?
To fix CVE-2026-31813, upgrade to Supabase Auth version 2.185.0 or later.
What software is affected by CVE-2026-31813?
CVE-2026-31813 affects Supabase Auth versions prior to 2.185.0.
What type of attack does CVE-2026-31813 enable?
CVE-2026-31813 enables attackers to issue sessions for arbitrary users using specially crafted ID tokens.
Is there a recommended action for users of Supabase Auth regarding CVE-2026-31813?
Users of Supabase Auth should immediately upgrade to the latest version to mitigate the risks associated with CVE-2026-31813.