CVE-2026-33409: Parse Server: Auth provider validation bypass on login via partial authData

Published Mar 19, 2026
·
Updated

Impact

An authentication bypass vulnerability allows an attacker to log in as any user who has linked a third-party authentication provider, without knowing the user's credentials. The attacker only needs to know the user's provider ID to gain full access to their account, including a valid session token.

This affects Parse Server deployments where the server option allowExpiredAuthDataToken is set to true. The default value is false.

Patches

Auth providers are now always validated on login, regardless of the allowExpiredAuthDataToken setting. The option allowExpiredAuthDataToken has been deprecated and will be removed in a future major version.

Workarounds

Set allowExpiredAuthDataToken to false (the default) or remove the option from the server configuration.

Other sources

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.52 and 9.6.0-alpha.41, an authentication bypass vulnerability allows an attacker to log in as any user who has linked a third-party authentication provider, without knowing the user's credentials. The attacker only needs to know the user's provider ID to gain full access to their account, including a valid session token. This affects Parse Server deployments where the server option allowExpiredAuthDataToken is set to true. The default value is false. This issue has been patched in versions 8.6.52 and 9.6.0-alpha.41.

MITRE

Affected Software

44 affected componentsFixes available
npm/parse-server<8.6.52
8.6.52
npm/parse-server>=9.0.0<9.6.0-alpha.41
9.6.0-alpha.41
parseplatform Parse-server Node.js<8.6.52
parseplatform Parse-server Node.js>=9.0.0<9.6.0
parseplatform Parse-server Node.js=9.6.0-alpha1
parseplatform Parse-server Node.js=9.6.0-alpha10
parseplatform Parse-server Node.js=9.6.0-alpha11
parseplatform Parse-server Node.js=9.6.0-alpha12
parseplatform Parse-server Node.js=9.6.0-alpha13
parseplatform Parse-server Node.js=9.6.0-alpha14
parseplatform Parse-server Node.js=9.6.0-alpha15
parseplatform Parse-server Node.js=9.6.0-alpha16
parseplatform Parse-server Node.js=9.6.0-alpha17
parseplatform Parse-server Node.js=9.6.0-alpha18
parseplatform Parse-server Node.js=9.6.0-alpha19
parseplatform Parse-server Node.js=9.6.0-alpha2
parseplatform Parse-server Node.js=9.6.0-alpha20
parseplatform Parse-server Node.js=9.6.0-alpha21
parseplatform Parse-server Node.js=9.6.0-alpha22
parseplatform Parse-server Node.js=9.6.0-alpha23
parseplatform Parse-server Node.js=9.6.0-alpha24
parseplatform Parse-server Node.js=9.6.0-alpha25
parseplatform Parse-server Node.js=9.6.0-alpha26
parseplatform Parse-server Node.js=9.6.0-alpha27
parseplatform Parse-server Node.js=9.6.0-alpha28
parseplatform Parse-server Node.js=9.6.0-alpha29
parseplatform Parse-server Node.js=9.6.0-alpha3
parseplatform Parse-server Node.js=9.6.0-alpha30
parseplatform Parse-server Node.js=9.6.0-alpha31
parseplatform Parse-server Node.js=9.6.0-alpha32
parseplatform Parse-server Node.js=9.6.0-alpha33
parseplatform Parse-server Node.js=9.6.0-alpha34
parseplatform Parse-server Node.js=9.6.0-alpha35
parseplatform Parse-server Node.js=9.6.0-alpha36
parseplatform Parse-server Node.js=9.6.0-alpha37
parseplatform Parse-server Node.js=9.6.0-alpha38
parseplatform Parse-server Node.js=9.6.0-alpha39
parseplatform Parse-server Node.js=9.6.0-alpha4
parseplatform Parse-server Node.js=9.6.0-alpha40
parseplatform Parse-server Node.js=9.6.0-alpha5
parseplatform Parse-server Node.js=9.6.0-alpha6
parseplatform Parse-server Node.js=9.6.0-alpha7
parseplatform Parse-server Node.js=9.6.0-alpha8
parseplatform Parse-server Node.js=9.6.0-alpha9

Event History

Mar 19, 2026
Advisory Published
via GitHub·09:32 PM
Data Sourced
via GitHub·09:32 PM
DescriptionWeaknessAffected Software
Mar 24, 2026
CVE Published
via MITRE·06:11 PM
Data Sourced
via MITRE·06:11 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 23, 58202
Event
via FIRST·02:32 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-33409?

CVE-2026-33409 is classified as a high severity vulnerability due to its ability to allow authentication bypass.

2

How do I fix CVE-2026-33409?

To fix CVE-2026-33409, upgrade to parse-server version 8.6.52 or 9.6.0-alpha.41.

3

What software is affected by CVE-2026-33409?

CVE-2026-33409 affects parse-server versions before 8.6.52 and between 9.0.0 and 9.6.0-alpha.41.

4

Can CVE-2026-33409 be exploited remotely?

Yes, CVE-2026-33409 can be exploited remotely by an attacker who knows the user's third-party provider ID.

5

What type of vulnerability is CVE-2026-33409?

CVE-2026-33409 is an authentication bypass vulnerability that compromises user accounts linked with third-party authentication providers.

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