CVE-2026-32242

Description

### 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

How to fix CVE-2026-32242

To remediate CVE-2026-32242, upgrade the affected package to a fixed version below.

• —upgrade to 8.6.37 or later
• —upgrade to 9.6.0-alpha.11 or later

Is CVE-2026-32242 being exploited?

Low — EPSS is 0.1%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0, < 8.6.37, >= 9.0.0, < 9.6.0
• >= 9.0.0, < 9.6.0-alpha.11

CVSS scores

References (5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-32242
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/releases/tag/8.6.37
• WEBgithub.com/parse-community/parse-server/releases/tag/9.6.0-alpha.11