CVE-2026-32943: Parse Server has a password reset token single-use bypass via concurrent requests
Impact
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.
Patches
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.
Workarounds
There is no known workaround other than upgrading.
Other sources
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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-32943?
CVE-2026-32943 has a medium severity rating due to the potential for unauthorized password resets.
How do I fix CVE-2026-32943?
To fix CVE-2026-32943, upgrade to Parse Server version 8.6.48 or 9.6.0-alpha.28 or later.
What is the impact of CVE-2026-32943?
The impact of CVE-2026-32943 is that it allows multiple concurrent requests to reuse a password reset token.
Which versions of Parse Server are affected by CVE-2026-32943?
Versions of Parse Server from 8.6.0 up to 8.6.48 and from 9.0.0 to 9.6.0-alpha.28 are affected by CVE-2026-32943.
What kind of vulnerability is CVE-2026-32943?
CVE-2026-32943 is a vulnerability related to the improper handling of password reset tokens, allowing for unauthorized access.