Skip to content

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

LowCVSS 2.3 EPSS 0.24%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

Description

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.

Upgrade path

3 packages: 2 fixed.

PackageAffectedFixed inStatus
npm parse-server(npm) < 8.6.48; >= 9.0.0, < 9.6.0-alpha.28 8.6.48, 9.6.0-alpha.28 Fixed
parseplatform parse-server < 8.6.48; = 9.6.0-alpha1; = 9.6.0-alpha2; = 9.6.0-alpha3 +25 more 8.6.48, 9.6.0 Fixed
parse-community parse-server = < 8.6.48; = >= 9.0.0, < 9.6.0-alpha.28 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
parse-community parse-server = >= 9.0.0, < 9.6.0-alpha.28 No fix listed
parse-community parse-server = < 8.6.48 No fix listed
npm parse-server(npm) >= 9.0.0, < 9.6.0-alpha.28 9.6.0-alpha.28
npm parse-server(npm) < 8.6.48 8.6.48
parseplatform parse-server < 8.6.48 8.6.48
parseplatform parse-server >= 9.0.0, < 9.6.0 9.6.0
parseplatform parse-server = 9.6.0-alpha1 No fix listed
parseplatform parse-server = 9.6.0-alpha10 No fix listed
parseplatform parse-server = 9.6.0-alpha11 No fix listed
parseplatform parse-server = 9.6.0-alpha12 No fix listed
parseplatform parse-server = 9.6.0-alpha13 No fix listed
parseplatform parse-server = 9.6.0-alpha14 No fix listed
parseplatform parse-server = 9.6.0-alpha15 No fix listed
parseplatform parse-server = 9.6.0-alpha16 No fix listed
parseplatform parse-server = 9.6.0-alpha17 No fix listed
parseplatform parse-server = 9.6.0-alpha18 No fix listed
parseplatform parse-server = 9.6.0-alpha19 No fix listed
parseplatform parse-server = 9.6.0-alpha2 No fix listed
parseplatform parse-server = 9.6.0-alpha20 No fix listed
parseplatform parse-server = 9.6.0-alpha21 No fix listed
parseplatform parse-server = 9.6.0-alpha22 No fix listed
parseplatform parse-server = 9.6.0-alpha23 No fix listed
parseplatform parse-server = 9.6.0-alpha24 No fix listed
parseplatform parse-server = 9.6.0-alpha25 No fix listed
parseplatform parse-server = 9.6.0-alpha26 No fix listed
Show 8 more
ProductAffected versionsFixed in
parseplatform parse-server = 9.6.0-alpha27 No fix listed
parseplatform parse-server = 9.6.0-alpha3 No fix listed
parseplatform parse-server = 9.6.0-alpha4 No fix listed
parseplatform parse-server = 9.6.0-alpha5 No fix listed
parseplatform parse-server = 9.6.0-alpha6 No fix listed
parseplatform parse-server = 9.6.0-alpha7 No fix listed
parseplatform parse-server = 9.6.0-alpha8 No fix listed
parseplatform parse-server = 9.6.0-alpha9 No fix listed

References