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 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
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | parse-server | >= 9.0.0, < 9.6.0-alpha.11, < 8.6.37 | 9.6.0-alpha.11, 8.6.37 |
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-2cjm-2gwv-m892
- https://nvd.nist.gov/vuln/detail/CVE-2026-32242
- https://github.com/parse-community/parse-server
- 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
- CVSS vector
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- Weakness (CWE)
CWE-362- Platform
- npm
- Package
parse-server- Disclosed
- 12.03.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-2cjm-2gwv-m892 - CC BY 4.0
Vulnerability history: parse-server
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 116
- First → latest
- 06.2019 06.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 17
- High 49
- Medium 40
- Low 10
Disclosures per year
- 2019: 2
- 2020: 4
- 2021: 4
- 2022: 12
- 2023: 5
- 2024: 4
- 2025: 6
- 2026: 79
-
Parse Server's OAuth2 adapter shares mutable state across providers via singleton instance this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.