Advisory

GHSA-r3xq-68wh-gwvh

Also known as: BIT-parse-2026-32943, CVE-2026-32943

Summary

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

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-03-17 17:40 UTC
Modified
2026-03-20 12:26 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0, fixed 9.6.0-alpha.28 (semver)

Fixed versions

9.6.0-alpha.28

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.48 (semver)

Fixed versions

8.6.48

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences