Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.8.0-alpha.6 and 8.6.74, he 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. This vulnerability is fixed in 9.8.0-alpha.6 and 8.6.74.
References
| Link | Resource |
|---|---|
| https://github.com/parse-community/parse-server/pull/10398 | Issue Tracking Patch |
| https://github.com/parse-community/parse-server/pull/10399 | Issue Tracking Patch |
| https://github.com/parse-community/parse-server/security/advisories/GHSA-mmpq-5hcv-hf2v | Mitigation Patch Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-04-07 18:16
Updated : 2026-06-17 10:41
NVD link : CVE-2026-39321
Mitre link : CVE-2026-39321
CVE.ORG link : CVE-2026-39321
JSON object : View
Products Affected
parseplatform
- parse-server
CWE
CWE-208
Observable Timing Discrepancy
