Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
8.2

Parse Server's MFA Recovery Codes Can be Used Multiple Times

GHSA-4hf6-3x24-c9m8 CVE-2026-31875
Summary

If you use multi-factor authentication (MFA) with Parse Server, an attacker could use a single recovery code to log in multiple times without the code being used only once. To fix this, update to Parse Server version 9.6.0-alpha.7 or 8.6.33.

What to do
  • Update parse-server to version 9.6.0-alpha.7.
  • Update parse-server to version 8.6.33.
Affected software
VendorProductAffected versionsFix available
parse-server > 9.0.0-alpha.1 , <= 9.6.0-alpha.7 9.6.0-alpha.7
parse-server <= 8.6.33 8.6.33
parseplatform parse-server <= 8.6.33
parseplatform parse-server > 9.0.0 , <= 9.6.0
parseplatform parse-server 9.6.0
parseplatform parse-server 9.6.0
parseplatform parse-server 9.6.0
parseplatform parse-server 9.6.0
parseplatform parse-server 9.6.0
parseplatform parse-server 9.6.0
Original title
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.7 and 8.6.33, when multi-factor authentication (MFA) via TOTP is enabled...
Original 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.7 and 8.6.33, when multi-factor authentication (MFA) via TOTP is enabled for a user account, Parse Server generates two single-use recovery codes. These codes are intended as a fallback when the user cannot provide a TOTP token. However, recovery codes are not consumed after use, allowing the same recovery code to be used an unlimited number of times. This defeats the single-use design of recovery codes and weakens the security of MFA-protected accounts. An attacker who obtains a single recovery code can repeatedly authenticate as the affected user without the code ever being invalidated. This vulnerability is fixed in 9.6.0-alpha.7 and 8.6.33.
ghsa CVSS4.0 8.2
Vulnerability type
CWE-672
Published: 11 Mar 2026 · Updated: 14 Mar 2026 · First seen: 11 Mar 2026