CVE-2026-31813 Supabase Auth has insecure Apple and Azure authentication with ID tokens
Attackers can hijack user accounts by crafting ID tokens when Apple or Azure providers are enabled, allowing unauthorized session issuance.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-31813?
CVE-2026-31813 is a medium-severity authentication bypass vulnerability in supabase auth, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-290
Which versions are affected by CVE-2026-31813?
It affects 1 product.
Products include Supabase Auth.
How do I fix CVE-2026-31813?
No fix has been published for CVE-2026-31813 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-31813 being exploited?
There is no known exploitation of CVE-2026-31813 in the wild and no public exploit code.
Sources
Also known as GHSA-v36f-qvww-8w8m.