CVE-2026-31875: Parse server Parse Server's MFA Recovery Codes Vulnerability

HIGH
Advisory Identifier: GHSA-4hf6-3x24-c9m8
CWE-672
Published
Advisory Summary

CVE-2026-31875 is a HIGH parse server's mfa recovery codes vulnerability (CWE-672: Operation on a Resource after Expiration or Release) affecting Parse server libraries in the npm ecosystem. The issue involves parse server's mfa recovery codes not consumed after use. Remediation is available by upgrading affected packages to version 9.6.0-alpha.7, 8.6.33.

CVE-2026-31875 at a Glance

CVE Identifier CVE-2026-31875
GHSA Identifier GHSA-4hf6-3x24-c9m8
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-672: Operation on a Resource after Expiration or Release
Affected Product Parse server
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-31875

To remediate this vulnerability, upgrade all affected Parse server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

parse-server fixed: 9.6.0-alpha.7
npm install parse-server@9.6.0-alpha.7
parse-server fixed: 8.6.33
npm install parse-server@8.6.33
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls parse-server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-31875, inspect your project dependencies using npm:

npm ls parse-server

Analyze the terminal output to locate any version of Parse server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.6.0-alpha.7), your application is affected.

Note: The npm ls parse-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-672: Operation on a Resource after Expiration or Release, where the product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked. In Parse server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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

CVE-2026-31875 Affected Parse server Versions

2 component(s)
Fixed Versions:
9.6.0-alpha.78.6.33
Product / Package Ecosystem Affected Versions Fixed Version
parse-server
npm
≥ 9.0.0-alpha.1
< 9.6.0-alpha.7
9.6.0-alpha.7
parse-server
npm
< 8.6.33
8.6.33

References

Frequently Asked Questions

What is CVE-2026-31875?
CVE-2026-31875 is a security vulnerability in Parse server involving Parse Server's MFA recovery codes not consumed after use under CWE-672: Operation on a Resource after Expiration or Release.
Which Parse server versions are affected?
Affected versions include releases prior to 9.6.0-alpha.7, 8.6.33 across affected packages: parse-server.
What version fixes CVE-2026-31875?
Upgrading to 9.6.0-alpha.7, 8.6.33 (or the latest patched release for your respective branch) resolves the vulnerability.
Is parse-server affected?
Yes, parse-server is affected in releases prior to 9.6.0-alpha.7, 8.6.33. Upgrade your dependency to 9.6.0-alpha.7, 8.6.33 or later.
What CWE is associated with CVE-2026-31875?
CVE-2026-31875 is classified under CWE-672: Operation on a Resource after Expiration or Release (The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.).
How can I check npm dependencies for CVE-2026-31875?
Run the dependency tree command: 'npm ls parse-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4hf6-3x24-c9m8",
  "modified" : "2026-03-11T20:57:55Z",
  "published" : "2026-03-11T00:35:41Z",
  "aliases" : [ "CVE-2026-31875" ],
  "summary" : "Parse Server's MFA recovery codes not consumed after use",
  "details" : "### Impact\n\nWhen 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.\n\nAn attacker who obtains a single recovery code can repeatedly authenticate as the affected user without the code ever being invalidated.\n\n### Patches\n\nThe fix ensures that each recovery code is removed from the stored recovery code list after a successful login.\n\n### Workarounds\n\nThere is no known workaround.\n\n### References\n\n- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-4hf6-3x24-c9m8\n- Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.7\n- Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.33",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.0.0-alpha.1"
      }, {
        "fixed" : "9.6.0-alpha.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.33"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-4hf6-3x24-c9m8"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-31875"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/releases/tag/8.6.33"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.7"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-672" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-11T00:35:41Z",
    "nvd_published_at" : "2026-03-11T18:16:27Z"
  }
}