Advisory

GHSA-2cjm-2gwv-m892

Also known as: BIT-parse-2026-32242, CVE-2026-32242

Summary

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

Details

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

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2026-03-12 17:29 UTC
Modified
2026-03-16 10:41 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0, fixed 9.6.0-alpha.11 (semver)

Fixed versions

9.6.0-alpha.11

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.37 (semver)

Fixed versions

8.6.37

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences