CVE-2026-32943

Description

### 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.

How to fix CVE-2026-32943

To remediate CVE-2026-32943, upgrade the affected package to a fixed version below.

• —upgrade to 8.6.48 or later
• —upgrade to 9.6.0-alpha.28 or later

Is CVE-2026-32943 being exploited?

Low — EPSS is 0.0%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0, < 8.6.48, >= 9.0.0, < 9.6.0
• >= 9.0.0, < 9.6.0-alpha.28

CVSS scores

References (5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-32943
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/pull/10216
• WEBgithub.com/parse-community/parse-server/pull/10217