cve.bz

CVE-2026-31901 parseplatform parse-server: Observable Response Discrepancy

6.3 mediumEPSS 0.3%Fix available

Medium (6.3) in parseplatform parse-server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in parse-server 8.6.34, 9.6.0-alpha.8.

On this page
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 8.6.34 and 9.6.0-alpha.8, the email verification endpoint (/verificationEmailRequest) returns distinct error responses depending on whether an email address belongs to an existing user, is already verified, or does not exist. An attacker can send requests with different email addresses and observe the error codes to determine which email addresses are registered in the application. This is a user enumeration vulnerability that affects any Parse Server deployment with email verification enabled (verifyUserEmails: true). This vulnerability is fixed in 8.6.34 and 9.6.0-alpha.8.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-03-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-204 Observable Response Discrepancy
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-31901 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-31901?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-31901?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-31901 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
parseplatform:parse-serverbefore 8.6.34
parseplatform:parse-serverfrom 9.0.0 before 9.6.0
parseplatform:parse-server9.6.0:alpha1
parseplatform:parse-server9.6.0:alpha2
parseplatform:parse-server9.6.0:alpha3
parseplatform:parse-server9.6.0:alpha4
parseplatform:parse-server9.6.0:alpha5
parseplatform:parse-server9.6.0:alpha6
parseplatform:parse-server9.6.0:alpha7

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-w54v-hf9p-8856npmparse-server>=9.0.0-alpha.1 <9.6.0-alpha.89.6.0-alpha.8
GHSA-w54v-hf9p-8856npmparse-server<8.6.348.6.34

Attack patterns (CAPEC)

  • CAPEC-331 ICMP IP Total Length Field Probe Likelihood: Medium · Severity: Low
  • CAPEC-332 ICMP IP 'ID' Field Error Message Probe Likelihood: Medium · Severity: Low
  • CAPEC-541 Application Fingerprinting Severity: Low
  • CAPEC-580 System Footprinting Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON