CVE-2026-39321: Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js

Q: How do I fix CVE-2026-39321?

parse-server: upgrade to 8.6.74, 9.8.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-39321 being exploited?

CVE-2026-39321 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-39321 affect?

CVE-2026-39321 affects parse-server. Severity is low (CVSS 3.7). 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 ema

Q: How urgent is CVE-2026-39321?

Priority 21/100. Remotely exploitable, no login, no user action

Routine

LOW 3.7REMOTEUPGRADE

CVE-2026-39321 is a low-severity flaw (CVSS 3.7) affecting parse-server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 differ

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	3.7 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 86%)
CISA exploited list	No
Weakness	CWE-208
Published	2026-04-07
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: parseplatform

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-07 18:16 UTCPublished CVE record published
2026-10-26 21:10 UTCUpdated Record last modified

parseplatform parse-server UPGRADE

Affected: < 8.6.74 · >= 9.0.0 and < 9.8.0 · 9.8.0 alpha1 · 9.8.0 alpha2 · 9.8.0 alpha3 · 9.8.0 alpha4 · 9.8.0 alpha5

Fixed in: 8.6.74, 9.8.0

Safe to downgrade to: a release before 9.0.0

1. Check installed version

npm ls parse-server

2. UPGRADE to 8.6.74

npm install parse-server@">=8.6.74"

3. If no update is available yet, DOWNGRADE to a release before 9.0.0

npm view parse-server versions npm install parse-server@"<9.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-39321?

parse-server: upgrade to 8.6.74, 9.8.0. Exact commands for each OS are on this page.

Is CVE-2026-39321 being exploited?

CVE-2026-39321 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-39321 affect?

CVE-2026-39321 affects parse-server. Severity is low (CVSS 3.7). 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 ema

How urgent is CVE-2026-39321?

Priority 21/100. Remotely exploitable, no login, no user action

Software pages

Node.js vulnerabilities

Related CVEs

CVE-2026-43930 MEDIUM 5.9 UPGRADE Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js
CVE-2021-47986 HIGH 7.5 DOWNGRADE Parse Server before 4.10.0 contains a supply chain vulnerability where incorrect version tags were pushed to t

References

← Back to latest CVEs