CVE-2026-39321: CWE-208: Observable Timing Discrepancy in parse-community parse-server
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.
AI Analysis
Technical Summary
Parse Server versions before 9.8.0-alpha.6 and 8.6.74 exhibit a timing side-channel vulnerability on the login endpoint. When a login attempt is made, the server responds immediately if the username or email is not found, but performs a bcrypt password hash comparison if the user exists, causing a measurable delay. This timing discrepancy allows attackers to determine valid usernames by measuring response times. The issue is classified under CWE-208 (Observable Timing Discrepancy). The vulnerability is addressed in versions 9.8.0-alpha.6 and 8.6.74.
Potential Impact
An unauthenticated attacker can enumerate valid usernames on the parse-server by exploiting the timing difference in login responses. This information disclosure can facilitate further targeted attacks such as password guessing or social engineering. There is no indication of direct code execution or data modification from this vulnerability alone.
Mitigation Recommendations
Upgrade parse-server to version 9.8.0-alpha.6 or later, or 8.6.74 or later, where this timing discrepancy vulnerability is fixed. No other mitigations are indicated. Patch status is confirmed fixed in these versions.
CVE-2026-39321: CWE-208: Observable Timing Discrepancy in parse-community parse-server
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Parse Server versions before 9.8.0-alpha.6 and 8.6.74 exhibit a timing side-channel vulnerability on the login endpoint. When a login attempt is made, the server responds immediately if the username or email is not found, but performs a bcrypt password hash comparison if the user exists, causing a measurable delay. This timing discrepancy allows attackers to determine valid usernames by measuring response times. The issue is classified under CWE-208 (Observable Timing Discrepancy). The vulnerability is addressed in versions 9.8.0-alpha.6 and 8.6.74.
Potential Impact
An unauthenticated attacker can enumerate valid usernames on the parse-server by exploiting the timing difference in login responses. This information disclosure can facilitate further targeted attacks such as password guessing or social engineering. There is no indication of direct code execution or data modification from this vulnerability alone.
Mitigation Recommendations
Upgrade parse-server to version 9.8.0-alpha.6 or later, or 8.6.74 or later, where this timing discrepancy vulnerability is fixed. No other mitigations are indicated. Patch status is confirmed fixed in these versions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-06T19:31:07.266Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d549ecaaed68159a473907
Added to database: 4/7/2026, 6:16:12 PM
Last enriched: 4/7/2026, 6:32:13 PM
Last updated: 4/8/2026, 12:46:22 AM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.