GitHub Advisoryadvisory · npm

GHSA-4hf6-3x24-c9m8 Parse Server's MFA recovery codes not consumed after use

HIGH Published 2026-03-11 Modified 2026-03-11 Official page ↗
Aliases
CVE-2026-31875
Ecosystem
npm
Packages
parse-server
Severity
High
CVSS vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Weaknesses
CWE-672
Reviewed
2026-03-11

Affected packages

• npm parse-server: >= 9.0.0-alpha.1, < 9.6.0-alpha.7 → fixed in 9.6.0-alpha.7 • npm parse-server: < 8.6.33 → fixed in 8.6.33

Description

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

Related

Alias · CVE (1)

  • CVE-2026-31875 Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. vulnerability

Weakness · CWE (1)

  • CWE-672 Operation on a Resource after Expiration or Release weakness

References