CVE-2026-32242: Parse Server's OAuth2 adapter shares mutable state across providers via singleton instance
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…
Published Mar 12, 2026 · Updated Mar 13, 2026
Affected packages
parse-server
- Ecosystem
- npm
- Affected
- >= 9.0.0, < 9.6.0-alpha.11
- Fixed in
- 9.6.0-alpha.11
- Check
npm ls parse-server
parse-server
- Ecosystem
- npm
- Affected
- < 8.6.37
- Fixed in
- 8.6.37
- Check
npm ls parse-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
Credited to fancymalware, mtrezza.
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-2cjm-2gwv-m892
- https://github.com/parse-community/parse-server/releases/tag/8.6.37
- https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.11
- https://nvd.nist.gov/vuln/detail/CVE-2026-32242
- https://github.com/advisories/GHSA-2cjm-2gwv-m892
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-34532
parse-server has cloud function validator bypass via prototype chain traversal
critical9.1Mar 31, 2026CVE-2026-32248
Parse Server: Account takeover via operator injection in authentication data identifier
critical9.3Mar 12, 2026CVE-2026-30965
Parse Server vulnerable to session token exfiltration via `redirectClassNameForKey` query parameter
critical9.9Mar 11, 2026CVE-2026-30966
Parse Server has role escalation and CLP bypass via direct `_Join` table write
critical10.0Mar 11, 2026CVE-2026-31856
Parse Server vulnerable to SQL injection via `Increment` operation on nested object field in PostgreSQL
critical9.3Mar 11, 2026CVE-2026-31871
Parse Server vulnerable to SQL Injection via dot-notation sub-key name in `Increment` operation on PostgreSQL
critical9.3Mar 11, 2026
