parse-server
Affected
- introduced
9.0.0, fixed9.6.0-alpha.12(semver)
Fixed versions
9.6.0-alpha.12
Fix
- Fixed version
9.6.0-alpha.12npm install [email protected]
Advisory
Also known as: BIT-parse-2026-32248, CVE-2026-32248
Parse Server: Account takeover via operator injection in authentication data identifier
Impact
An unauthenticated attacker can take over any user account that was created with an authentication provider that does not validate the format of the user identifier (e.g. anonymous authentication). By sending a crafted login request, the attacker can cause the server to perform a pattern-matching query instead of an exact-match lookup, allowing the attacker to match an existing user and obtain a valid session token for that user's account. Both MongoDB and PostgreSQL database backends are affected. Any Parse Server deployment that allows anonymous authentication (enabled by default) is vulnerable.
Patches
The fix enforces that the user identifier in authentication data is a string before using it in a database query. Non-string values are rejected with a validation error.
Workarounds
There is no known workaround.
References
Critical Basis: The source's own band: CRITICAL
9.0.0, fixed 9.6.0-alpha.12 (semver)9.6.0-alpha.12
9.6.0-alpha.12npm install [email protected]0, fixed 8.6.38 (semver)8.6.38
8.6.38npm 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