CVE-2026-101042

published 27 Sep 2026 · updated 30 Sep 2026

Parse Server 9.0.0 Authentication Bypass via Unverified Provider Identity

6.4MediumCVSS 6.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 8.6.91 and 9.10.1-alpha.10.

Parse Server is an open-source backend server. In versions >= 9.0.0 < 9.10.1-alpha.10 and >= 8.0.2 < 8.6.91, the code-based authentication adapters (GitHub, Google Play Games, Instagram, LINE, LinkedIn, Microsoft, QQ, Spotify, WeChat, Weibo) verify the client's authorization code with the external provider on signup and on provider linking, but not when authentication data is supplied together with a username and password on the login endpoint. As a result, a low-privileged authenticated user can attach an arbitrary, unverified provider identity to their own account without the provider ever being contacted, spoofing an external identity toward application logic that trusts the linked provider ID. An attacker can also pre-hijack accounts: by claiming the provider ID of a victim who has not yet linked that provider, the victim's later legitimate sign-in with that provider resolves to the attacker's account. Only deployments configuring one of the affected code-based auth adapters are impacted. Versions 9.10.1-alpha.10 and 8.6.91 fix the issue by running the adapter's credential verification on the login and challenge endpoints and rejecting a provider identity already linked to another user. As a workaround, disable the affected code-based auth adapters.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
parse-community>=8.0.2 <8.6.91, >=9.0.0 <9.10.1-alpha.108.6.91, 9.10.1-alpha.10

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-101042 severity on Zeptric[![CVE-2026-101042](https://zeptric.io/badge/cve/CVE-2026-101042.svg)](https://zeptric.io/cve/CVE-2026-101042)