CVE-2026-31875: Parse Server Multi-Factor Authentication Recovery Code Vulnerability
Summary
CVE-2026-31875: Parse Server's MFA recovery codes not consumed after use. Affects parse-server across 2 version ranges.
< 8.6.33
>= 9.0.0-alpha.1, < 9.6.0-alpha.7
Fixed in 8.6.33 or 9.6.0-alpha.7, depending on the release line you run. How to fix ↓
Also tracked for
- parse · Bitnami
The same CVE-2026-31875 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Parse Server is an open-source backend platform that enables developers to build applications quickly by providing a range of features such as data storage, user authentication, and real-time notifications. It supports multi-factor authentication (MFA) to enhance security, allowing users to authenticate using Time-based One-Time Passwords (TOTP) along with recovery codes for fallback. However, a critical vulnerability has been identified in the way recovery codes are managed, potentially compromising user accounts.
Vulnerability Detail
The vulnerability arises from the failure to consume single-use recovery codes after they are utilized for authentication. When MFA is enabled, Parse Server generates two recovery codes intended for one-time use. However, these codes remain valid indefinitely, allowing an attacker who gains access to a recovery code to repeatedly authenticate as the affected user. This undermines the purpose of MFA and poses a significant security risk, as it enables unauthorized access to user accounts without the need for valid TOTP tokens.
How To Fix
Latest published version: 9.10.5 as of 22 Oct 2026
npm install parse-server@9.10.5Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 8.6.338.6.33npm install parse-server@8.6.33 -
>= 9.0.0-alpha.1, < 9.6.0-alpha.79.6.0-alpha.7npm install parse-server@9.6.0-alpha.7
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no known workaround for this vulnerability. The only effective solution is to update to the patched versions of Parse Server.
Conclusion
The vulnerability CVE-2026-31875 in Parse Server poses a significant risk by allowing recovery codes for multi-factor authentication to be reused. It is crucial for developers using affected versions to update to the latest patched versions to ensure the security of user accounts. Monitoring tools like Vulert can assist in identifying such vulnerabilities in your dependencies.
See every vulnerability recorded for parse-server →
FAQ
CVE-2026-31875 is a vulnerability in Parse Server that allows recovery codes for multi-factor authentication to be reused, compromising account security.
If your application uses Parse Server with MFA enabled, an attacker could exploit this vulnerability to gain unauthorized access to user accounts using the same recovery code multiple times.
You should immediately update to the patched versions of Parse Server (9.6.0-alpha.7 or 8.6.33) to mitigate the risk associated with this vulnerability.
Currently, there are no known workarounds. Updating to the patched version is the only solution.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
Related vulnerabilities
Recent vulnerabilities recorded for parse-server.
