Which versions of Node.js are affected by CVE-2026-33624?

CVE-2026-33624 is a low-severity vulnerability in Parse Server (CVSS 2.1). The limited severity suggests constrained impact, typically requiring specific conditions or local access for exploitation.. A patch is available.

How to fix or mitigate CVE-2026-33624?

During next maintenance window: Apply vendor patches when convenient. Monitor vendor channels for updates.

Node.js CVE-2026-33624

Q: What is the CVSS score of CVE-2026-33624?

CVE-2026-33624 has a CVSS 4.0 base score of 2.1 (Low). CVSS vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-14978 LOW

Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)

2026-03-24 GitHub_M

Information Disclosure Node.js Parse Server Parse Community

2.1

CVSS 4.0 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

2.1 LOW

CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

High

Privileges Required

High

User Interaction

None

Scope

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

EUVD ID Assigned

Mar 24, 2026 - 19:00 euvd

EUVD-2026-14978

Analysis Generated

Mar 24, 2026 - 19:00 vuln.today

CVE Published

Mar 24, 2026 - 18:28 nvd

LOW 2.1

DescriptionGitHub Advisory

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.60 and 9.6.0-alpha.54, an attacker who obtains a user's password and a single MFA recovery code can reuse that recovery code an unlimited number of times by sending concurrent login requests. This defeats the single-use design of recovery codes. The attack requires the user's password, a valid recovery code, and the ability to send concurrent requests within milliseconds. This issue has been patched in versions 8.6.60 and 9.6.0-alpha.54.

AnalysisAI

Parse Server versions prior to 8.6.60 and 9.6.0-alpha.54 contain a race condition vulnerability that allows attackers to reuse single-use MFA recovery codes an unlimited number of times through concurrent login requests. An attacker with knowledge of a user's password and possession of one valid recovery code can bypass the intended single-use restriction by sending multiple authentication attempts simultaneously within milliseconds, effectively defeating the multi-factor authentication protection mechanism. This vulnerability is tracked as CWE-367 (TOCTOU race condition) and has been patched in the aforementioned versions with fixes available via pull requests 10275 and 10276.

Technical ContextAI

Parse Server is a Node.js-based open-source backend framework that provides multi-factor authentication (MFA) capabilities including recovery code functionality. The vulnerability stems from a time-of-check-to-time-of-use (TOCTOU) race condition in the MFA recovery code validation logic, classified under CWE-367. The affected product is identified via CPE as cpe:2.3:a:parse-community:parse-server, spanning versions from the initial implementation through 8.6.59 and all pre-release versions of the 9.x branch prior to 9.6.0-alpha.54. The root cause involves insufficient synchronization or atomic operations when verifying and invalidating recovery codes, allowing a single valid code to be validated by multiple concurrent requests before any single request can mark it as consumed. This is a classic application-level race condition that exploits the gap between code validation and state update in the authentication workflow.

RemediationAI

Immediately upgrade Parse Server to version 8.6.60 or later for stable releases, or to version 9.6.0-alpha.54 or later for those using the 9.x pre-release branch. The patches implement proper synchronization of recovery code validation and invalidation as detailed in commits 5e70094250a36bfcc14ecd49592be2b94fba66ff and fc3da35a81d5083b453e8967cabcc880f1a3bd0c, with supporting changes in pull requests 10275 and 10276. Organizations unable to patch immediately should consider temporary mitigations such as temporarily disabling recovery code functionality until patching is feasible, or implementing additional application-level rate limiting on login attempts per user account. Review MFA logs for patterns consistent with concurrent recovery code reuse attempts. Once patching is complete, validate the deployment and consider forcing password resets for any accounts that may have been compromised during the vulnerability window.