parse-server
Affected
- introduced
9.0.0, fixed9.8.0-alpha.6(semver)
Fixed versions
9.8.0-alpha.6
Fix
- Fixed version
9.8.0-alpha.6npm install [email protected]
Advisory
Also known as: BIT-parse-2026-39321, CVE-2026-39321
Parse Server has a login timing side-channel reveals user existence
Impact
The login endpoint response time differs measurably depending on whether the submitted username or email exists in the database. When a user is not found, the server responds immediately. When a user exists but the password is wrong, a bcrypt comparison runs first, adding significant latency. This timing difference allows an unauthenticated attacker to enumerate valid usernames.
Patches
A dummy bcrypt comparison is now performed when no user is found, normalizing response timing regardless of user existence. Additionally, accounts without a stored password (e.g. OAuth-only) now also run a dummy comparison to prevent the same timing oracle.
Workarounds
Configure rate limiting on the login endpoint to slow automated enumeration. This reduces throughput but does not eliminate the timing signal for individual requests.
Medium Basis: The source's own band: MODERATE
9.0.0, fixed 9.8.0-alpha.6 (semver)9.8.0-alpha.6
9.8.0-alpha.6npm install [email protected]0, fixed 8.6.74 (semver)8.6.74
8.6.74npm 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