Password Reset Token Bypass in Parse Server: A Critical Security Flaw

parse-server Updated 17 Mar 2026

Summary

17/03/2026
LOW
Yes i
Low
2.3

GHSA-r3xq-68wh-gwvh: Parse Server has a password reset token single-use bypass via concurrent requests. Affects parse-server across 2 version ranges.

< 8.6.48 >= 9.0.0, < 9.6.0-alpha.28

Fixed in 8.6.48 or 9.6.0-alpha.28, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Parse Server is an open-source backend framework that enables developers to build applications without the need for a custom server. It provides features such as data storage, user authentication, and real-time notifications. However, a vulnerability has been identified in its password reset mechanism, which allows attackers to exploit the system by bypassing single-use guarantees for reset tokens.

Vulnerability Detail

The vulnerability arises from the password reset mechanism in Parse Server, which does not enforce single-use guarantees for reset tokens. When a user requests a password reset, the generated token can be consumed by multiple concurrent requests. This flaw allows an attacker who intercepts a reset token to race against the legitimate user's request, leading to both requests being processed successfully. Consequently, the legitimate user may believe their password has been changed, while the attacker's password takes effect instead. This vulnerability affects all Parse Server deployments that utilize the password reset feature.

How To Fix

Latest published version: 9.10.5 as of 22 Oct 2026

npm install parse-server@9.10.5

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 8.6.48 8.6.48
    npm install parse-server@8.6.48
  • >= 9.0.0, < 9.6.0-alpha.28 9.6.0-alpha.28
    npm install parse-server@9.6.0-alpha.28

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There are no known workarounds for this vulnerability other than upgrading to the patched version of Parse Server.

Conclusion

The identified vulnerability in Parse Server's password reset mechanism poses a significant risk by allowing attackers to exploit reset tokens. It is essential for developers using Parse Server to upgrade to the latest patched versions to ensure the security of their applications and protect user data.

See every vulnerability recorded for parse-server →

Share this vulnerability

FAQ

The vulnerability allows multiple concurrent requests to use the same password reset token, enabling an attacker to potentially change a user's password without their consent.

If your application uses Parse Server for password resets and is running a version prior to the patched releases (9.6.0-alpha.28 or 8.6.48), it is likely affected.

While there are no workarounds, it is crucial to prioritize upgrading to the patched version as soon as possible to mitigate the risk.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground.

The CVSS score for this vulnerability is 2.3, indicating a low severity level.

Related vulnerabilities

Recent vulnerabilities recorded for parse-server.

How To Fix

Latest published version: 9.10.5 as of 22 Oct 2026

npm install parse-server@9.10.5

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 8.6.48 8.6.48
    npm install parse-server@8.6.48
  • >= 9.0.0, < 9.6.0-alpha.28 9.6.0-alpha.28
    npm install parse-server@9.6.0-alpha.28

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback