parse-server
Affected
- introduced
9.0.0, fixed9.9.0-alpha.2(semver)
Fixed versions
9.9.0-alpha.2
Fix
- Fixed version
9.9.0-alpha.2npm install [email protected]
Advisory
Also known as: BIT-parse-2026-43930, CVE-2026-43930
parse-server: MFA SMS one-time password accepted twice under concurrent login
Impact
A race condition in the MFA SMS one-time password (OTP) login path allows two concurrent /login requests carrying the same OTP to both succeed and both receive valid session tokens, breaking the single-use property of the OTP. The vulnerability requires the attacker to already possess the victim's password and intercept the active SMS OTP (e.g. via SIM swap, network mirror, or phishing relay) and to race the legitimate login request, so the practical attack surface is narrow.
This advisory is the same class of incomplete fix as GHSA-2299-ghjr-6vjp (TOTP recovery codes) and GHSA-w73w-g5xw-rwhf (MFA recovery in authData-only login). Those previous fixes added optimistic locking only for array-typed authData fields; SMS MFA stores the OTP as a string, so the guard skipped it.
Patches
The optimistic lock has been generalized to cover primitive (string, number, boolean) and array authData fields. The lock is implemented as a shared helper applyAuthDataOptimisticLock that adds equality predicates on the original values of changed fields to the update WHERE clause. Concurrent writers racing the same single-use token now miss the WHERE condition and surface as Invalid auth data.
Workarounds
/login endpoint to reduce concurrent-request burst capacity.Resources
Low Basis: The source's own band: LOW
9.0.0, fixed 9.9.0-alpha.2 (semver)9.9.0-alpha.2
9.9.0-alpha.2npm install [email protected]0, fixed 8.6.76 (semver)8.6.76
8.6.76npm install [email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0