CVE-2026-31875

Description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.7 and 8.6.33, 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. This vulnerability is fixed in 9.6.0-alpha.7 and 8.6.33.

Overview

State: PUBLISHED
Assigner (CNA): GitHub_M
CVSS severity: HIGH
CVSS score: 8.2 / 10
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
Effective score: 8.2 / 10 HIGH source: CNA overview
CWE(s): CWE-672
Reserved: 2026-03-09
Published: 2026-03-11 19:04 UTC
Last updated: 2026-03-12 21:06 UTC
Source: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/31xxx/CVE-2026-31875.json
Linked Threat: CVE-2026-31875 — Parse Server MFA recovery codes not consumed after use

NVD triage scoring NVD CVE 2.0

Layer NVD adds on top of the CNA's CVE record — published / last-modified timestamps, exploitability / impact subscores, and the FIRST.org EPSS probability that this CVE will be exploited in the wild in the next 30 days.

NVD published: 2026-03-11 18:16:27 UTC
NVD last modified: 2026-03-13 17:15:25 UTC
NVD CVSS v3.1: 5.9 / 10 MEDIUM source: nvd@nist.gov
NVD CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploitability subscore: 2.2 / 10
Impact subscore: 3.6 / 10
EPSS score: 0.0014 (probability of exploitation in next 30 days)
EPSS percentile: 33.42% vs all CVEs — higher = more likely to be exploited, as of 2026-05-25

European Union Vulnerability Database ENISA EUVD

ENISA's official EU repository for curated vulnerability intelligence. Carries a separate identifier (EUVD-YYYY-NNNN) and frequently exposes an earlier-published description + CVSS than NVD does.

EUVD ID: EUVD-2026-11280
Assigner: GitHub_M
Published: Mar 11, 2026, 6:04:55 PM
Updated: Mar 12, 2026, 8:06:19 PM
EUVD base score (CVSS 4.0): 8.2 / 10
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
EUVD-reported EPSS: 0.1400
Vendors: parse-community
Products: parse-server (9.0.0 < 9.6.0-alpha.7)

parse-server (< 8.6.33)
Aliases: GHSA-4hf6-3x24-c9m8

ENISA description: Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.7 and 8.6.33, 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. This vulnerability is fixed in 9.6.0-alpha.7 and 8.6.33.

EUVD references (3)

Affected products (1)

Vendor	Product	Versions	Platforms
parse-community	parse-server	`>= 9.0.0 < 9.6.0-alpha.7` (affected), `< 8.6.33` (affected)	—

Affected products — CPE 2.3 (7) NVD

NVD's normalized CPE 2.3 matchers, used by vendor tools (vulnerability scanners, asset managers) for automated detection. Compare with the CNA's free-text "Affected products" section above.

cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:node.js:*:*
cpe:2.3:a:parseplatform:parse-server:9.6.0:alpha1:*:*:*:node.js:*:*
cpe:2.3:a:parseplatform:parse-server:9.6.0:alpha2:*:*:*:node.js:*:*
cpe:2.3:a:parseplatform:parse-server:9.6.0:alpha3:*:*:*:node.js:*:*
cpe:2.3:a:parseplatform:parse-server:9.6.0:alpha4:*:*:*:node.js:*:*
cpe:2.3:a:parseplatform:parse-server:9.6.0:alpha5:*:*:*:node.js:*:*
cpe:2.3:a:parseplatform:parse-server:9.6.0:alpha6:*:*:*:node.js:*:*

Vendor references (3)

References embedded in the original CVE record by the assigning CNA.

https://github.com/parse-community/parse-server/security/advisories/GHSA-4hf6-3x24-c9m8 x_refsource_CONFIRM
https://github.com/parse-community/parse-server/releases/tag/8.6.33 x_refsource_MISC
https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.7 x_refsource_MISC

MITRE references (3) cveawg.mitre.org

Pulled from MITRE's CVE Services API by the 🛰 Backfill from MITRE button.

https://github.com/parse-community/parse-server/releases/tag/8.6.33 x_refsource_MISC
https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.7 x_refsource_MISC
https://github.com/parse-community/parse-server/security/advisories/GHSA-4hf6-3x24-c9m8 x_refsource_CONFIRM

Web references (0)

DuckDuckGo results ranked by threat-intel / vendor advisory domains. Generated by the 🔎 Find references (web) button above — same flow as the Remediations search.

No web references attached yet.

NVD-tagged references (3)

Reference list NVD curates from the CNA record, vendor advisories, and third-party reports. The tag chips below are NVD's analyst-assigned categories.

https://github.com/parse-community/parse-server/releases/tag/8.6.33 security-advisories@github.com ProductRelease Notes
https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.7 security-advisories@github.com ProductRelease Notes
https://github.com/parse-community/parse-server/security/advisories/GHSA-4hf6-3x24-c9m8 security-advisories@github.com PatchVendor Advisory

Indicators (1)

IOCs linked to the auto-promoted Threat row.

Type	Value	VirusTotal	Attached
domain	`node.js`	no local data	2026-05-18 21:18 UTC

Remediations (16)

Remediations are stored against the linked Threat row; the list below is deduplicated across both pages.

Microsoft and Adobe Patch Tuesday, April 2026 Security Update Review

web:blog.qualys.com

With Qualys Policy Audit's out-of-the-box mitigation or Compensatory Controls, which reduce the risk of a vulnerability being exploited because the remediation ( fix / patch ) cannot be done immediately, these security controls are not recommended by any industry standards, such as CIS and DISA-STIG.

2026-05-22 16:40 UTC
Microsoft Patch Tuesday March 2026 - 78 Vulnerabilities Fixed ...

web:cybersecuritynews.com

Microsoft released its March 2026 Patch Tuesday security update on March 10, 2026 , addressing 78 vulnerabilities across Windows, Microsoft Office, Azure, SQL Server, and .NET. The update includes one actively exploited zero-day vulnerability and multiple Critical-rated flaws demanding immediate attention from security teams. The most urgent fix this month is CVE - 2026 -21262, the sole zero-day ...

2026-05-22 16:40 UTC
Microsoft Security Advisory CVE-2026-32175 - .NET Core ... - GitHub

web:github.com

Executive Summary: Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 8.0, .NET 9.0, and .NET 10.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A tampering vulnerability exists when .NET Core improperly handles specially crafted files. An attacker who successfully ...

2026-05-22 16:40 UTC
CVEs, vulnerabilities, and security advisories for Broadcom, CA ...

web:knowledge.broadcom.com

Find information about potential security risks that affect Broadcom, CA, Symantec, Carbon Black and VMware products, and their available patches and remediation .

2026-05-22 16:40 UTC
Critical Patches Issued for Microsoft Products, May 12, 2026

web:www.cisecurity.org

<p>Multiple vulnerabilities have been discovered in Microsoft products, the most severe of which could allow for remote code execution. Successful exploitation of the most severe of these vulnerabilities could result in an attacker gaining the same privileges as the logged-on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or ...

2026-05-22 16:40 UTC
April 2026 Patch Tuesday: Updates and Analysis | CrowdStrike

web:www.crowdstrike.com

Microsoft's April 2026 Patch Tuesday addresses 164 CVEs , featuring 8 Critical vulnerabilities, one exploited zero-day, and one disclosed zero-day.

2026-05-22 16:40 UTC
Security Update Guide - Microsoft

web:portal.msrc.microsoft.com

The Security Update Guide provides information on the latest Microsoft security updates, helping users understand and address potential vulnerabilities effectively.

2026-05-22 04:19 UTC
Microsoft Rushes to Mitigate Dangerous New "YellowKey" Windows Exploit

web:windowsreport.com

The newly exposed Windows security flaw, dubbed "YellowKey," has become a major headache for Microsoft. After the exploit details leaked publicly alongside a working proof-of-concept, the company has now rushed out official mitigation guidance while it prepares a permanent fix . The vulnerability reportedly targets BitLocker-protected systems and could allow attackers direct access to ...

2026-05-22 04:19 UTC
Microsoft Rolls Out Mitigations for 'YellowKey' BitLocker ...

web:www.securityweek.com

Microsoft has announced mitigations for CVE - 2026 -45585, a BitLocker bypass triggered via FsTx in Windows Recovery.

2026-05-22 04:19 UTC
Patch Tuesday May 2026: Security Updates & CVE Analysis

web:zecurit.com

Get the complete breakdown of Microsoft's May 2026 Patch Tuesday. We analyze the latest security updates and all critical CVEs .

2026-05-22 04:19 UTC
Grammarly: Free AI Writing Assistance

web:www.grammarly.com

Grammarly makes AI writing convenient. Work smarter with personalized AI guidance and text generation on any app or website.

2026-05-22 04:19 UTC
Microsoft and Adobe Patch Tuesday, May 2026 Security Update Review

web:blog.qualys.com

May 2026's Patch Tuesday arrives with Microsoft addressing a fresh set of vulnerabilities across its ecosystem, reinforcing the ongoing need for timely patching in an increasingly threat-heavy…

2026-05-22 04:19 UTC
Microsoft provides mitigation for "YellowKey" BitLocker bypass flaw ...

web:www.helpnetsecurity.com

Microsoft is working on a fix for CVE - 2026 -45585 (aka "Yellowkey"), a vulnerability that can be used to bypass Windows' BitLocker protection.

2026-05-22 04:19 UTC
Microsoft Releases Mitigation for Windows BitLocker Security Bypass 0 ...

web:cybersecuritynews.com

Microsoft has disclosed a critical zero-day vulnerability in Windows BitLocker, tracked as CVE - 2026 -45585, that allows threat actors with physical access to bypass full-disk encryption entirely, potentially exposing sensitive data within minutes.

2026-05-22 04:19 UTC
Microsoft Rushes Out Emergency Mitigation For 'YellowKey ... - LinkedIn

web:www.linkedin.com

Microsoft Security Response Center has issued an emergency mitigation for a newly disclosed BitLocker bypass vulnerability known as "YellowKey," after security researchers publicly released ...

2026-05-22 04:19 UTC
Oracle Critical Patch Update Advisory - April 2026

web:www.oracle.com

This Critical Patch Update contains 481 new security patches across the product families listed below. Please note that an MOS note summarizing the content of this Critical Patch Update and other Oracle Software Security Assurance activities is located at April 2026 Critical Patch Update: Executive Summary and Analysis.

2026-05-22 04:19 UTC

AI Forensic Analysis

Only Available for Registered Users. Sign in to view.

Raw JSON

The full cvelistV5 record. Download as CVE-2026-31875.json.

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-31875",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-03-12T20:06:08.618428Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-03-12T20:06:19.822Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "parse-server",
          "vendor": "parse-community",
          "versions": [
            {
              "status": "affected",
              "version": ">= 9.0.0 < 9.6.0-alpha.7"
            },
            {
              "status": "affected",
              "version": "< 8.6.33"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.7 and 8.6.33, 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. This vulnerability is fixed in 9.6.0-alpha.7 and 8.6.33."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 8.2,
            "baseSeverity": "HIGH",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "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",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "NONE"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-672",
              "description": "CWE-672: Operation on a Resource after Expiration or Release",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-03-11T18:04:55.700Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/parse-community/parse-server/security/advisories/GHSA-4hf6-3x24-c9m8",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/parse-community/parse-server/security/advisories/GHSA-4hf6-3x24-c9m8"
        },
        {
          "name": "https://github.com/parse-community/parse-server/releases/tag/8.6.33",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/parse-community/parse-server/releases/tag/8.6.33"
        },
        {
          "name": "https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.7",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.7"
        }
      ],
      "source": {
        "advisory": "GHSA-4hf6-3x24-c9m8",
        "discovery": "UNKNOWN"
      },
      "title": "Parse Server MFA recovery codes not consumed after use"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-31875",
    "datePublished": "2026-03-11T18:04:55.700Z",
    "dateReserved": "2026-03-09T19:02:25.014Z",
    "dateUpdated": "2026-03-12T20:06:19.822Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}