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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- 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
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.3 · parseplatformNVD modified 2026-10-26 21:10
Affected (CPE criteria) 6
cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:node.js:*:*cpe:2.3:a:parseplatform:parse-server:9.8.0:alpha1:*:*:*:node.js:*:*cpe:2.3:a:parseplatform:parse-server:9.8.0:alpha2:*:*:*:node.js:*:*cpe:2.3:a:parseplatform:parse-server:9.8.0:alpha3:*:*:*:node.js:*:*cpe:2.3:a:parseplatform:parse-server:9.8.0:alpha4:*:*:*:node.js:*:*cpe:2.3:a:parseplatform:parse-server:9.8.0:alpha5:*:*:*:node.js:*:*
References 3
- 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