Summary
Parse Server's MFA recovery codes not consumed after use
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
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The fix ensures that each recovery code is removed from the stored recovery code list after a successful login.
Frequently Asked Questions
- What is CVE-2026-31875? CVE-2026-31875 is a high-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0-alpha.1, < 9.6.0-alpha.7. It is fixed in 9.6.0-alpha.7, 8.6.33.
- Which versions of parse-server are affected by CVE-2026-31875? parse-server (npm) versions >= 9.0.0-alpha.1, < 9.6.0-alpha.7 is affected.
- Is there a fix for CVE-2026-31875? Yes. CVE-2026-31875 is fixed in 9.6.0-alpha.7, 8.6.33. Upgrade to this version or later.
- Is CVE-2026-31875 exploitable, and should I be worried? Whether CVE-2026-31875 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-31875 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-31875?
- Upgrade
parse-serverto 9.6.0-alpha.7 or later - Upgrade
parse-serverto 8.6.33 or later
- Upgrade