Cyber Resilience

CVE-2026-39321

Parseplatform Parse-Server ≤ 8.6.74

Published
07 April 2026
Modified
15 April 2026
Patch / advisory
View advisory
CVSS Score v4 6.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0023 14th percentile
Risk Priority 30 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-39321 is a medium-severity Observable Timing Discrepancy (CWE-208) vulnerability in Parseplatform Parse-Server. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Password Guessing (T1110.001); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-208

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
attack.mitre.org →
T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
attack.mitre.org →
T1087.001 Local Account Discovery
Adversaries may attempt to get a listing of local system accounts.
attack.mitre.org →
T1087.002 Domain Account Discovery
Adversaries may attempt to get a listing of domain accounts.
attack.mitre.org →
T1087.003 Email Account Discovery
Adversaries may attempt to get a listing of email addresses and accounts.
attack.mitre.org →
T1087.004 Cloud Account Discovery
Adversaries may attempt to get a listing of cloud accounts.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-33323Same product: Parseplatform Parse-Server
CVE-2026-31901Same product: Parseplatform Parse-Server
CVE-2026-33429Same product: Parseplatform Parse-Server
CVE-2026-30972Same product: Parseplatform Parse-Server
CVE-2026-33627Same product: Parseplatform Parse-Server
CVE-2026-33163Same product: Parseplatform Parse-Server
CVE-2026-34215Same product: Parseplatform Parse-Server
CVE-2026-32098Same product: Parseplatform Parse-Server
CVE-2026-35200Same product: Parseplatform Parse-Server
CVE-2026-30938Same product: Parseplatform Parse-Server

Affected Assets

parseplatform
parse-server
9.8.0 · ≤ 8.6.74 · 9.0.0 — 9.8.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V11.2.4

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing can include timing analysis or side-channel test cases that reveal observable timing discrepancies.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can mandate constant-time algorithms and side-channel resistance so timing discrepancies are never introduced.

SC-13 Cryptographic Protection partial match

Requiring approved cryptographic modules and algorithms implicitly demands implementations free of observable timing leaks.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require constant-time implementations that eliminate observable timing discrepancies.

References