Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.1
Parse Server's OAuth2 adapter can validate wrong provider's tokens
GHSA-2cjm-2gwv-m892
CVE-2026-32242
Summary
If you're using multiple OAuth2 providers with Parse Server, a bug can let a token be accepted even if it shouldn't be. This happens because the same instance of the OAuth2 adapter is used for all providers. To fix this, upgrade to Parse Server version 9.6.0-alpha.11 or 8.6.37.
What to do
- Update parse-server to version 9.6.0-alpha.11.
- Update parse-server to version 8.6.37.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| – | parse-server | > 9.0.0 , <= 9.6.0-alpha.11 | 9.6.0-alpha.11 |
| – | parse-server | <= 8.6.37 | 8.6.37 |
| parseplatform | parse-server | <= 8.6.37 | – |
| parseplatform | parse-server | > 9.0.0 , <= 9.6.0 | – |
| parseplatform | parse-server | 9.6.0 | – |
| parseplatform | parse-server | 9.6.0 | – |
| parseplatform | parse-server | 9.6.0 | – |
| parseplatform | parse-server | 9.6.0 | – |
| parseplatform | parse-server | 9.6.0 | – |
| parseplatform | parse-server | 9.6.0 | – |
| parseplatform | parse-server | 9.6.0 | – |
| parseplatform | parse-server | 9.6.0 | – |
| parseplatform | parse-server | 9.6.0 | – |
| parseplatform | parse-server | 9.6.0 | – |
Original title
Parse Server's OAuth2 adapter shares mutable state across providers via singleton instance
Original 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
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
ghsa CVSS4.0
9.1
Vulnerability type
CWE-362
Race Condition
- https://github.com/parse-community/parse-server/security/advisories/GHSA-2cjm-2g...
- 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://github.com/advisories/GHSA-2cjm-2gwv-m892
- https://nvd.nist.gov/vuln/detail/CVE-2026-32242
Published: 12 Mar 2026 · Updated: 14 Mar 2026 · First seen: 12 Mar 2026