What is the CVSS score of CVE-2026-32242?

CVE-2026-32242 has a CVSS 3.1 base score of 7.4 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for CVE-2026-32242?

Yes, a public proof-of-concept exploit is available for CVE-2026-32242. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2026-32242?

Within 24 hours: Inventory all Parse Server instances and identify those configured with multiple OAuth2 providers—these are at immediate risk. Within 7 days: Implement compensating controls by disabling non-critical OAuth2 providers or reducing concurrent authentication capacity. Within 30 days: Immediately deploy the vendor patch when available, or migrate to an alternative authentication solution if Parse Server cannot be patched within your change management window.

Parse Server CVE-2026-32242

HIGH

Race Condition (CWE-362)

2026-03-12 security-advisories@github.com

GHSA-2cjm-2gwv-m892

Information Disclosure Node.js Race Condition Parse Server Parseplatform

7.4

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Send concurrent OAuth2 authentication requests
Exploit

Singleton instance processes requests with mismatched provider configs
Execution

Token validated against wrong provider's policy
Impact

Unauthorized access granted

Vulnerability Assessment

Weakness	CWE CWE-362 OWASP Top 10:2025 A06:2025 - Insecure Design ASVS 5.0 V15 - Secure Coding and Architecture Concurrency control, locking MITRE ATT&CK 1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Parse Server versions prior to 9.6.0-alpha.11 or 8.6.37 with multiple OAuth2 providers configured and concurrent authentication requests enabled. Requires specific timing of simultaneous requests to different OAuth2 providers.
Impact	Can lead to privilege escalation, data corruption, or bypassing of security checks depending on the context of the race.
Exploit ScenarioDerived	An attacker exploits a time-of-check-time-of-use (TOCTOU) window to modify a resource between when it's validated and when it's used.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Impact

Parse Server's built-in OAuth2 auth adapter exports a singleton instance that is reused directly across all OAuth2 provider configurations. Under concurrent authentication requests for different OAuth2 providers, one provider's token validation may execute using another provider's configuration, potentially allowing a token that should be rejected by one provider to be accepted because it is validated against a different provider's policy.

Deployments that configure multiple OAuth2 providers via the oauth2: true flag are affected.

Patches

The fix ensures that a new adapter instance is created for each provider instead of reusing the singleton, so each provider's configuration is isolated.

Workarounds

There is no known workaround. If only a single OAuth2 provider is configured, the race condition cannot occur.

References

GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-2cjm-2gwv-m892
Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.11
Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.37

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 19:57 CVSS 7.4

RemediationAI

Use proper synchronization mechanisms (locks, mutexes, atomic operations). Implement file locking for filesystem operations. Avoid TOCTOU patterns.

Affected Packages

npm parse-server fix: 8.6.37, 9.6.0-alpha.11

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

A race condition occurs when the behavior of software depends on the timing of events, such as the order of execution of threads or processes.

Know when Parse Server gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.4 HIGH

AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

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

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

PoC Detected

Mar 13, 2026 - 16:57 vuln.today

Public exploit code

CVE Published

Mar 12, 2026 - 19:16 nvd

HIGH 7.4

DescriptionGitHub Advisory

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.11 and 8.6.37, Parse Server's built-in OAuth2 auth adapter exports a singleton instance that is reused directly across all OAuth2 provider configurations. Under concurrent authentication requests for different OAuth2 providers, one provider's token validation may execute using another provider's configuration, potentially allowing a token that should be rejected by one provider to be accepted because it is validated against a different provider's policy. Deployments that configure multiple OAuth2 providers via the oauth2: true flag are affected. This vulnerability is fixed in 9.6.0-alpha.11 and 8.6.37.

Executive ViewAI

Why It Matters

Parse Server deployments using multiple OAuth2 providers are vulnerable to authentication bypass attacks due to a race condition in token validation logic. An attacker could exploit concurrent requests to use one provider's valid token to authenticate through another provider's system, potentially gaining unauthorized access to accounts across different identity providers.

Business Impact: High

Compensating Controls

Reduce OAuth2 provider configurations to a single provider if business logic permits; implement request-level rate limiting and queue management to minimize concurrent authentication requests; deploy WAF rules to detect and block suspicious multi-provider authentication patterns; segregate OAuth2 authentication traffic to isolated infrastructure to limit blast radius; enforce strict network segmentation around Parse Server instances; monitor authentication logs for cross-provider token reuse patterns.

Threat Intelligence Overview

EPSS Score

0.1%

Top 76% exploitable

Exploit

POC

Public exploit code exists

Data Quality

5 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.1%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

Poc

System Exposure· derived

Open

Automatable· derived

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +37

PoC: +20

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Race Condition MEDIUM

Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).