Parse Server 9.0.0 Authentication Bypass via Unverified Provider Identity

Summary

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.

Timeline

1. Sep 27, 2026, 4:28 PM UTCCVE published
2. Sep 30, 2026, 3:27 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Sep 30, 2026, 3:28 PM UTCRecord last updated

Affected versions

• parse-community parse-server

  From 9.0.0 · fixed in 9.10.1-alpha.10

• parse-community parse-server

  From 8.0.2 · fixed in 8.6.91

• parseBitnami

  From 8.0.2 · fixed in 8.6.91; From 9.0.0 · fixed in 9.10.1

References 2