Parse Server has an auth provider validation bypass on login via partial authData
GHSA-pfj7-wv7c-22pr · BIT-parse-2026-33409 · CVE-2026-33409
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
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.
References
- WEB https://github.com/parse-community/parse-server/security/advisories/GHSA-pfj7-wv7c-22pr
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-33409
- WEB https://github.com/parse-community/parse-server/pull/10246
- WEB https://github.com/parse-community/parse-server/pull/10247
- WEB https://github.com/parse-community/parse-server/commit/8d7df5639c4a35768fe8b78b4580b30e8a74721c
- WEB https://github.com/parse-community/parse-server/commit/98f4ba5bcf2c199bfe6225f672e8edcd08ba732d
- PACKAGE https://github.com/parse-community/parse-server
Ready to move
Start Securing
Free, no credit card | First findings in minutes