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%.

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

Parse Server deployments using multiple OAuth2 providers are vulnerable to authentication bypass attacks due to a race condition in token validation logic.. A patch is available.

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.

Node.js CVE-2026-32242

HIGH

Race Condition (CWE-362)

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

GHSA-2cjm-2gwv-m892

Node.js Race Condition Information Disclosure Parse Server

7.4

CVSS 3.1 · GitHub Advisory

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

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

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

Analysis Generated

Mar 12, 2026 - 19:57 vuln.today

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.

AnalysisAI

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