Parse Server's OAuth2 adapter shares mutable state across providers via singleton instance

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.1 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-32242: 0.27% estimated exploitation activity in the next 30 days; percentile 19.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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:…

Published by the source

12 Mar 2026, 17:29 UTC

Last modified by the source

16 Mar 2026, 10:41 UTC

Source last checked

26 Oct 2026, 12:46 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2cjm-2gwv-m892

2. Revision 3 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-2cjm-2gwv-m892

4. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-2cjm-2gwv-m892

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32242

Advisory: Parse Server's OAuth2 adapter shares mutable state across providers via singleton instance
IDs: CVE-2026-32242, GHSA-2cjm-2gwv-m892
Record: https://patchnext.com/advisories/cve-2026-32242 (revision 4, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: parse-server 9.6.0-alpha.11, 8.6.37. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm parse-server: affected >= 9.0.0, < 9.6.0-alpha.11; < 8.6.37; fixed in 8.6.37, 9.6.0-alpha.11

## Suggested inspection (read-only)
- `npm ls parse-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on parse-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2cjm-2gwv-m892 (GitHub-reviewed advisory GHSA-2cjm-2gwv-m892 lists affected ranges: npm parse-server >=9.0.0 =0 <8.6.37)
- Verified: https://osv.dev/vulnerability/GHSA-2cjm-2gwv-m892 (OSV record GHSA-2cjm-2gwv-m892 lists affected ranges: npm parse-server >=9.0.0 =0 <8.6.37 (fixed))

Commands are suggestions: review each one before running it.