Advisory

GHSA-4hf6-3x24-c9m8

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

Summary

Parse Server's MFA recovery codes not consumed after use

Details

Impact

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.

Patches

The fix ensures that each recovery code is removed from the stored recovery code list after a successful login.

Workarounds

There is no known workaround.

References

  • GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-4hf6-3x24-c9m8
  • Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.7
  • Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.33

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-03-11 00:35 UTC
Modified
2026-03-13 13:10 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

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

Fixed versions

9.6.0-alpha.7

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.33 (semver)

Fixed versions

8.6.33

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