CVE-2026-116163: Parse Server 9.0.0 before 9.10.5 Authentication Bypass via AuthAdapter Subclasses

Published Oct 25, 2026
·
Updated

Parse Server before 8.6.102 and 9.0.0 before 9.10.5 contains an authentication bypass because the validateSetUp, validateLogin, and validateUpdate methods of custom adapters subclassing AuthAdapter are never called, and an inherited default that accepts any authData is used instead. Attackers can supply arbitrary authData to sign up, link identities, log in as existing users, or skip custom additional authentication factors.

Other sources

Parse Server before 8.6.102 and 9.0.0 before 9.10.5-alpha.2 contains an authentication bypass because the validateSetUp, validateLogin, and validateUpdate methods of custom adapters subclassing AuthAdapter are never called, and an inherited default that accepts any authData is used instead. Attackers can supply arbitrary authData to sign up, link identities, log in as existing users, or skip custom additional authentication factors.

— NVD

Affected Software

3 affected componentsFixes available
Parse Platform Parse Server<8.6.102, >=9.0.0<9.10.5-alpha.2
bitnami/parse<8.6.102
8.6.102
bitnami/parse>=9.0.0<9.10.5
9.10.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 8.6.102
  2. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 9.10.5-alpha.2

Event History

Oct 25, 2026
CVE Published
via MITRE·01:20 PM
Data Sourced
via MITRE·01:20 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeakness
Oct 30, 2026
Advisory Published
via OSV·03:35 PM
Data Sourced
via OSV·03:35 PM
Affected Software

Frequently Asked Questions

1

Which deployments are affected?

Deployments using Parse Server before 8.6.102, or versions from 9.0.0 before 9.10.5-alpha.2, are affected when they use a custom authentication adapter that subclasses AuthAdapter.

2

What must an attacker have to exploit this issue?

The vector is network-accessible and requires neither prior privileges nor user interaction. Exploitation has high attack complexity, but an attacker can provide arbitrary authData where the vulnerable custom adapter is used.

3

Does this affect installations that do not use custom AuthAdapter subclasses?

The described bypass is specific to custom adapters subclassing AuthAdapter. It occurs because their validateSetUp, validateLogin, and validateUpdate methods are not called and the inherited default accepts authData.

4

How can administrators identify whether their authentication flow is exposed?

Review custom authentication adapters that subclass AuthAdapter and determine whether they rely on validateSetUp, validateLogin, or validateUpdate to reject invalid authData or enforce additional authentication factors. Those validation methods are not invoked on affected versions.

5

What version should be deployed to address the issue?

Upgrade Parse Server to 8.6.102 or later, or to 9.10.5-alpha.2 or later for the 9.x release line.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203