Is CVE-2026-39321 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-39321 being exploited in the wild.

How severe is CVE-2026-39321?

Low severity, with a CVSS score of 3.7, published 7 April 2026.

Which products and versions are affected?

parse-server (npm) SEMVER:introduced=9.0.0,fixed=9.8.0-alpha.6.

Is there a fix for CVE-2026-39321?

Yes. parse-server (npm): upgrade to 9.8.0-alpha.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-39321 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-39321?

Check whether you run parse-server (npm) or Parseplatform Parse-Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-39321: Parse Community Parse Server timing side-channel in login endpoint

CVE-2026-39321 · Severity: low · CVSS 3.7 · Published 2026-04-07

Parse Server is an open-source backend framework used to power mobile and web applications. A vulnerability in its login system allows unauthorized individuals to determine if a specific username or email address exists in the database by measuring how long the server takes to respond. This could lead to the exposure of user lists, which can be used for targeted phishing or credential-guessing attacks.

Technologies: parse-server (npm). Vendors: npm.

Quick answers

Is CVE-2026-39321 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-39321 being exploited in the wild.
How severe is CVE-2026-39321?: Low severity, with a CVSS score of 3.7, published 7 April 2026.
Which products and versions are affected?: parse-server (npm) SEMVER:introduced=9.0.0,fixed=9.8.0-alpha.6.
Is there a fix for CVE-2026-39321?: Yes. parse-server (npm): upgrade to 9.8.0-alpha.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-39321 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-39321?: Check whether you run parse-server (npm) or Parseplatform Parse-Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

parse-server (npm): upgrade to 9.8.0-alpha.6 or later
```
npm install parse-server@9.8.0-alpha.6
```

Technical details

A timing side-channel vulnerability (CWE-208) exists in the Parse Server login endpoint. The server's response time varies significantly depending on whether a user exists: if a user is found, the server performs a computationally expensive bcrypt password comparison; if the user does not exist, it returns a response immediately. This discrepancy allows an unauthenticated attacker to perform username enumeration via network-based timing analysis. The issue has been addressed in versions 8.6.74 and 9.8.0-alpha.6 by implementing a dummy bcrypt comparison when a user is not found, thereby normalizing response times.

Affected products

Parse Community parse-server >= 9.0.0, < 9.8.0-alpha.6; < 8.6.74

Identifiers

CVE-2026-39321
GHSA-mmpq-5hcv-hf2v

Timeline

2026-04-05: disclosed: Initial disclosure by mtrezza
2026-04-07: advisory: NVD publication
2026-04-08: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.