What is CVE-2026-34215?

CVE-2026-34215 is a high-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.7.0-alpha.7. It is fixed in 9.7.0-alpha.7, 8.6.63.

Which versions of parse-server are affected by CVE-2026-34215?

parse-server (npm) versions >= 9.0.0, < 9.7.0-alpha.7 is affected.

Is there a fix for CVE-2026-34215?

Yes. CVE-2026-34215 is fixed in 9.7.0-alpha.7, 8.6.63. Upgrade to this version or later.

Is CVE-2026-34215 exploitable, and should I be worried?

Whether CVE-2026-34215 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-34215 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-34215?

Upgrade: parse-server to 9.7.0-alpha.7 or later, parse-server to 8.6.63 or later.

CVE-2026-34215 in parse-server

Q: Which versions of parse-server are affected by CVE-2026-34215?

parse-server (npm) versions >= 9.0.0, < 9.7.0-alpha.7 is affected.

Q: Is there a fix for CVE-2026-34215?

Yes. CVE-2026-34215 is fixed in 9.7.0-alpha.7, 8.6.63. Upgrade to this version or later.

Q: Is CVE-2026-34215 exploitable, and should I be worried?

Whether CVE-2026-34215 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-34215 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

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

Upgrade: parse-server to 9.7.0-alpha.7 or later, parse-server to 8.6.63 or later.

Summary

Parse Server exposes auth data via verify password endpoint

Workarounds

There is no known workaround.

Impact

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.

Affected versions

parse-server (>= 9.0.0, < 9.7.0-alpha.7) parse-server (< 8.6.63)

Security releases

parse-server → 9.7.0-alpha.7 (npm) parse-server → 8.6.63 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The verify password endpoint now sanitizes authentication data through auth adapter hooks before returning the response, consistent with login and user retrieval endpoints.

Frequently Asked Questions

What is CVE-2026-34215? CVE-2026-34215 is a high-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.7.0-alpha.7. It is fixed in 9.7.0-alpha.7, 8.6.63.
Which versions of parse-server are affected by CVE-2026-34215? parse-server (npm) versions >= 9.0.0, < 9.7.0-alpha.7 is affected.
Is there a fix for CVE-2026-34215? Yes. CVE-2026-34215 is fixed in 9.7.0-alpha.7, 8.6.63. Upgrade to this version or later.
Is CVE-2026-34215 exploitable, and should I be worried? Whether CVE-2026-34215 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-34215 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-34215?
- Upgrade parse-server to 9.7.0-alpha.7 or later
- Upgrade parse-server to 8.6.63 or later

Other vulnerabilities in parse-server

CVE-IDSeverityPackage summary

GHSA-97PR-9HGG-3P8RLowparse-server: parse-server: LiveQuery discloses object data to a subscriber across an ACL read-access change CVE-2026-55778Lowparse-server: parse-server: Stored XSS via non-standard file extension bypassing file upload extension blocklist CVE-2026-53726Mediumparse-server: parse-server: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL CVE-2026-53725Mediumparse-server: parse-server: Endpoints `/login` and `/verifyPassword` disclose MFA secrets and protected fields when `_User` get is denied CVE-2026-53724Lowparse-server: parse-server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist