cve.bz

CVE-2026-34215 parseplatform parse-server

8.2 highEPSS 0.3%Fix available

High (8.2) in parseplatform parse-server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in parse-server 8.6.63, 9.7.0-alpha.7.

On this page
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.63 and 9.7.0-alpha.7, the verify password endpoint returns unsanitized authentication data, including MFA TOTP secrets, recovery codes, and OAuth access tokens. An attacker who knows a user's password can extract the MFA secret to generate valid MFA codes, defeating multi-factor authentication protection. This issue has been patched in versions 8.6.63 and 9.7.0-alpha.7.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 26th 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-04-03. 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-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-34215 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34215?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34215?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-34215 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.63
parseplatform:parse-serverfrom 9.0.0 before 9.7.0
parseplatform:parse-server9.7.0:alpha1
parseplatform:parse-server9.7.0:alpha2
parseplatform:parse-server9.7.0:alpha3
parseplatform:parse-server9.7.0:alpha4
parseplatform:parse-server9.7.0:alpha5
parseplatform:parse-server9.7.0:alpha6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-wp76-gg32-8258npmparse-server>=9.0.0 <9.7.0-alpha.79.7.0-alpha.7
GHSA-wp76-gg32-8258npmparse-server<8.6.638.6.63

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON