Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Parse Server 9.0.0 Authentication Bypass via Unverified Provider Identity

CVSS 4.0 7.4 HIGHCVSS 3.1 6.4 MEDIUMCheck source for fixed versionsKEV status unknown

Historical advisory recorded 23 Oct 2026 15:48:27 UTC. Read the latest advisory.

cve-program · CVE-2026-101042

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-101042

Published

parse-server

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "parse-community",
                    "product": "parse-server",
                    "defaultStatus": "unaffected",
                    "packageURL": "pkg:npm/parse-server",
                    "versions": [
                        {
                            "version": "9.0.0",
                            "status": "affected",
                            "versionType": "semver",
                            "lessThan": "9.10.1-alpha.10"
                        },
                        {
                            "version": "9.10.1-alpha.10",
                            "status": "unaffected",
                            "versionType": "semver"
                        }
                    ]
                }

parse-server

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "parse-community",
                    "product": "parse-server",
                    "defaultStatus": "unaffected",
                    "packageURL": "pkg:npm/parse-server",
                    "versions": [
                        {
                            "version": "8.0.2",
                            "status": "affected",
                            "versionType": "semver",
                            "lessThan": "8.6.91"
                        },
                        {
                            "version": "8.6.91",
                            "status": "unaffected",
                            "versionType": "semver"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 12 Nov 18:36 UTC · 273 of 275 readable · 271 fully read · documentation 469/469 current