CVE-2026-34224

CVE-2026-34224 is a low-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.7.0-alpha.8. It is fixed in 9.7.0-alpha.8, 8.6.64.

Summary

Workarounds

There is no known workaround.

Impact

An attacker who possesses a valid authentication provider token and a single MFA recovery code or SMS one-time password can create multiple authenticated sessions by sending concurrent login requests via the authData login endpoint. This defeats the single-use guarantee of MFA recovery codes and SMS one-time passwords, allowing session persistence even after the legitimate user revokes detected sessions.

Affected versions

parse-server (>= 9.0.0, < 9.7.0-alpha.8) parse-server (< 8.6.64)

Security releases

parse-server → 9.7.0-alpha.8 (npm) parse-server → 8.6.64 (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.

See it in your environment

Remediation advice

The fix adds optimistic locking to the authData login path, ensuring that concurrent database updates for the same user fail when the original MFA token array has already been modified by another request.

Frequently Asked Questions

  1. What is CVE-2026-34224? CVE-2026-34224 is a low-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.7.0-alpha.8. It is fixed in 9.7.0-alpha.8, 8.6.64.
  2. Which versions of parse-server are affected by CVE-2026-34224? parse-server (npm) versions >= 9.0.0, < 9.7.0-alpha.8 is affected.
  3. Is there a fix for CVE-2026-34224? Yes. CVE-2026-34224 is fixed in 9.7.0-alpha.8, 8.6.64. Upgrade to this version or later.
  4. Is CVE-2026-34224 exploitable, and should I be worried? Whether CVE-2026-34224 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
  5. What actually determines whether CVE-2026-34224 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.
  6. How do I fix CVE-2026-34224?
    • Upgrade parse-server to 9.7.0-alpha.8 or later
    • Upgrade parse-server to 8.6.64 or later

Other vulnerabilities in parse-server

CVE-2026-55778CVE-2026-53726CVE-2026-53725CVE-2026-53724CVE-2026-50008

Stop the waste.
Protect your environment with Kodem.