parse-server
Affected
- introduced
9.0.0, fixed9.6.0-alpha.41(semver)
Fixed versions
9.6.0-alpha.41
Fix
- Fixed version
9.6.0-alpha.41npm install [email protected]
Advisory
Also known as: BIT-parse-2026-33409, CVE-2026-33409
Parse Server has an auth provider validation bypass on login via partial authData
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.
High Basis: The source's own band: HIGH
9.0.0, fixed 9.6.0-alpha.41 (semver)9.6.0-alpha.41
9.6.0-alpha.41npm install [email protected]0, fixed 8.6.52 (semver)8.6.52
8.6.52npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0