CVE-2026-31813

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-31813", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-03-09T16:33:42.914Z", "datePublished": "2026-03-11T16:42:56.606Z", "dateUpdated": "2026-03-11T17:20:20.728Z"}, "containers": {"cna": {"title": "Supabase Auth has insecure Apple and Azure authentication with ID tokens", "problemTypes": [{"descriptions": [{"cweId": "CWE-290", "lang": "en", "description": "CWE-290: Authentication Bypass by Spoofing", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 4.8, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N", "version": "3.1"}}], "references": [{"name": "https://github.com/supabase/auth/security/advisories/GHSA-v36f-qvww-8w8m", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/supabase/auth/security/advisories/GHSA-v36f-qvww-8w8m"}], "affected": [{"vendor": "supabase", "product": "auth", "versions": [{"version": "< 2.185.0", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-03-11T16:42:56.606Z"}, "descriptions": [{"lang": "en", "value": "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."}], "source": {"advisory": "GHSA-v36f-qvww-8w8m", "discovery": "UNKNOWN"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-31813", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-03-11T17:06:54.980041Z"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-03-11T17:20:20.728Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-31813", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-03-11T17:06:54.980041Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-03-11T17:14:15.360Z"}}], "cna": {"title": "Supabase Auth has insecure Apple and Azure authentication with ID tokens", "source": {"advisory": "GHSA-v36f-qvww-8w8m", "discovery": "UNKNOWN"}, "metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.8, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}}], "affected": [{"vendor": "supabase", "product": "auth", "versions": [{"status": "affected", "version": "< 2.185.0"}]}], "references": [{"url": "https://github.com/supabase/auth/security/advisories/GHSA-v36f-qvww-8w8m", "name": "https://github.com/supabase/auth/security/advisories/GHSA-v36f-qvww-8w8m", "tags": ["x_refsource_CONFIRM"]}], "descriptions": [{"lang": "en", "value": "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."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-290", "description": "CWE-290: Authentication Bypass by Spoofing"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-03-11T16:42:56.606Z"}}}, "cveMetadata": {"cveId": "CVE-2026-31813", "state": "PUBLISHED", "dateUpdated": "2026-03-11T17:20:20.728Z", "dateReserved": "2026-03-09T16:33:42.914Z", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "datePublished": "2026-03-11T16:42:56.606Z", "assignerShortName": "GitHub_M"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"product": "auth", "vendor": "supabase", "versions": [{"status": "affected", "version": "< 2.185.0"}]}], "source": "security-advisories@github.com"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:supabase:auth:*:*:*:*:*:*:*:*", "matchCriteriaId": "3B8F521E-D938-41A7-9CD8-453D430D33CD", "versionEndExcluding": "2.185.0", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Supabase Auth es una API basada en JWT para gestionar usuarios y emitir tokens JWT. Antes de la versi\u00f3n 2.185.0, se ha identificado una vulnerabilidad que permite a un atacante emitir sesiones para usuarios arbitrarios utilizando tokens de ID especialmente dise\u00f1ados cuando los proveedores de Apple o Azure est\u00e1n habilitados. El atacante emite un token de ID v\u00e1lido, firmado asim\u00e9tricamente, desde su emisor para cada direcci\u00f3n de correo electr\u00f3nico de la v\u00edctima, el cual luego se env\u00eda al endpoint de tokens de Supabase Auth utilizando el flujo de tokens de ID. Si el token de ID cumple con OIDC, el servidor de Auth lo validar\u00eda contra el emisor controlado por el atacante y vincular\u00eda la identidad OIDC existente (Apple o Azure) de la v\u00edctima a una identidad OIDC adicional basada en el contenido del token de ID. El servidor de Auth emitir\u00eda entonces una sesi\u00f3n de usuario v\u00e1lida (tokens de acceso y de actualizaci\u00f3n) en el nivel AAL1 al atacante. Esta vulnerabilidad est\u00e1 corregida en la versi\u00f3n 2.185.0."}], "id": "CVE-2026-31813", "lastModified": "2026-06-17T10:34:30.390", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 4.8, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N", "version": "3.1"}, "exploitabilityScore": 2.2, "impactScore": 2.5, "source": "security-advisories@github.com", "type": "Secondary"}, {"cvssData": {"attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 4.8, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N", "version": "3.1"}, "exploitabilityScore": 2.2, "impactScore": 2.5, "source": "nvd@nist.gov", "type": "Primary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-31813", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-03-11T17:06:54.980041Z", "version": "2.0.3"}}]}, "published": "2026-03-11T17:16:58.107", "references": [{"source": "security-advisories@github.com", "tags": ["Vendor Advisory"], "url": "https://github.com/supabase/auth/security/advisories/GHSA-v36f-qvww-8w8m"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-290"}], "source": "security-advisories@github.com", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[0,2.185.0)"}}], "enrichment": {"confidence": 100.0, "confidence_source": "cna", "scores": [{"score": 100.0, "source": "cna"}]}, "original": {"product": "auth", "source": "cna", "vendor": "supabase"}, "product": "auth", "vendor": "supabase"}], "analysis": {"en": {"generated_at": "2026-03-20T15:29:50.352030+00:00", "value": {"mitigation_remediation": ["Apply the Supabase Auth patch to version 2.185.0 or later", "If unable to upgrade immediately, disable Apple and Azure authentication providers in your Supabase Auth configuration", "Review and monitor authentication logs for any unusual activity"], "summary": {"action": "Apply Patch", "impact": "Account Impersonation"}, "threat_synthesis": {"affected_systems": "The vulnerability affects Supabase Auth for all versions older than 2.185.0. Any deployment using Supabase Auth 2.x (or earlier) with the Apple or Azure authentication provider enabled is potentially compromised. The vendor product cpe is cpe:2.3:a:supabase:auth:*:*:*:*:*:*:*:*.", "description_and_impact": "Supabase Auth, a JWT\u2011based service that manages users and issues JWT tokens, has a flaw in versions prior to 2.185.0 that permits an attacker to create valid sessions for any user. By forging an asymmetrically signed ID token that appears to come from a legitimate issuer (Apple or Azure) and contains the target user\u2019s email, the attacker submits this token to the Auth token endpoint. The server, trusting the issuer and verifying the token, associates the victim\u2019s existing OIDC identity with the attacker\u2019s identity and issues a new access and refresh token at the AAL1 level. This allows the attacker to impersonate the victim, gaining full read\u2011write access to the victim\u2019s account and any resources protected by Supabase Auth. The weakness is a failure to properly limit the trust in external ID tokens (CWE\u2011290).", "risk_and_exploitability": "The CVSS score of 4.8 indicates a moderate impact, with a low probability of exploitation (EPSS <1%) and no listing in the CISA KEV catalog. Exploitation requires an attacker to possess a valid private signing key for a custom Apple or Azure issuer set up in the Supabase Auth instance, as well as the ability to perform HTTP requests to the token endpoint. Because the attack path is remote and the attacker must control the token issuer, the likelihood of successful exploitation in the wild is low, but organizations with exposed Apple or Azure providers should prioritize patching. Once patched in version 2.185.0, the vulnerability is resolved."}}}}, "created": "2026-03-12T09:57:46.099817+00:00", "updated": "2026-03-23T09:55:23.875870+00:00", "vendors": ["supabase", "supabase$PRODUCT$auth"]}