← Back to the live CVE advisory feed

CVE-2026-101042: parse-server

Severity

7.4 (HIGH)

Vendor

PARSE-COMMUNITY

Affected versions

9.0.0 through before 9.10.1-alpha.10; 8.0.2 through before 8.6.91

Fixed version

9.10.1-alpha.10

Patch status

Patched

Published

2026-09-27T17:16:55.820

Modified

2026-09-27T17:16:55.820

Why it matters

This matters because the affected product may allow code execution. Prioritize systems that are internet-facing or have privileged access to other infrastructure.

Recommended admin actions

• Review and patch based on exposure, asset criticality, and business impact.
• Review logs for suspicious activity related to the affected application or component.

Technical 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.

View the official NVD record for CVE-2026-101042

CVE data is sourced from NVD/CNA records and optional enrichment. Validate against the vendor advisory before taking production action.