Vulnerability Description
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.
CVSS Score
LOW
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Parseplatform | Parse-Server | < 8.6.74 |
Related Weaknesses (CWE)
References
- https://github.com/parse-community/parse-server/pull/10398Issue TrackingPatch
- https://github.com/parse-community/parse-server/pull/10399Issue TrackingPatch
- https://github.com/parse-community/parse-server/security/advisories/GHSA-mmpq-5hMitigationPatchVendor Advisory
FAQ
What is CVE-2026-39321?
CVE-2026-39321 is a vulnerability with a CVSS score of 3.7 (LOW). 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 ...
How severe is CVE-2026-39321?
CVE-2026-39321 has been rated LOW with a CVSS base score of 3.7/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-39321?
Check the references section above for vendor advisories and patch information. Affected products include: Parseplatform Parse-Server.