Parse Server has a password reset token single-use bypass via concurrent requests

Summary

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.28 and 8.6.48, the password reset mechanism 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 within a short time window. An attacker who has intercepted a password reset token can race the legitimate user's password reset request, causing both requests to succeed. This may result in the legitimate user believing their password was changed successfully while the attacker's password takes effect instead. All Parse Server deployments that use the password reset feature are affected. Starting in versions 9.6.0-alpha.28 and 8.6.48, the password reset token is now atomically validated and consumed as part of the password update operation. The database query that updates the password includes the reset token as a condition, ensuring that only one concurrent request can successfully consume the token. Subsequent requests using the same token will fail because the token has already been cleared. There is no known workaround other than upgrading.

Timeline

1. Mar 18, 2026, 9:46 PM UTCCVE published
2. Mar 19, 2026, 3:48 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Mar 19, 2026, 3:49 PM UTCRecord last updated

Affected versions

• parse-community parse-server

  From 9.0.0 · fixed in 9.6.0-alpha.28; fixed in 8.6.48

• parse-servernpm

  From 9.0.0 · fixed in 9.6.0-alpha.28

• parse-servernpm

  fixed in 8.6.48

References 3