CVE-2026-32269: Parse Server OAuth2 adapter app ID validation sends wrong token to introspection endpoint
Impact
The OAuth2 authentication adapter does not correctly validate app IDs when appidField and appIds are configured. During app ID validation, a malformed value is sent to the token introspection endpoint instead of the user's actual access token. Depending on the introspection endpoint's behavior, this could either cause all OAuth2 logins to fail, or allow authentication from disallowed app contexts if the endpoint returns valid-looking data for the malformed request.
Deployments using the OAuth2 adapter with appidField and appIds configured are affected.
Patches
The fix corrects the parameter alignment in the OAuth2 adapter's app ID validation method to match the expected interface, ensuring the correct access token is sent to the introspection endpoint.
Workarounds
There is no known workaround.
References
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-69xg-f649-w5g2 - Fix in Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.13 - Fix in Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.39
Other sources
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.13 and 8.6.39, the OAuth2 authentication adapter does not correctly validate app IDs when appidField and appIds are configured. During app ID validation, a malformed value is sent to the token introspection endpoint instead of the user's actual access token. Depending on the introspection endpoint's behavior, this could either cause all OAuth2 logins to fail, or allow authentication from disallowed app contexts if the endpoint returns valid-looking data for the malformed request. Deployments using the OAuth2 adapter with appidField and appIds configured are affected. This vulnerability is fixed in 9.6.0-alpha.13 and 8.6.39.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-32269?
CVE-2026-32269 is considered a high severity vulnerability due to its potential impact on OAuth2 authentication.
How do I fix CVE-2026-32269?
To fix CVE-2026-32269, upgrade to Parse Server version 9.6.0-alpha.13 or 8.6.39 or later.
What causes CVE-2026-32269?
CVE-2026-32269 is caused by the OAuth2 adapter not correctly validating app IDs when sending tokens.
Which versions of Parse Server are affected by CVE-2026-32269?
Parse Server versions prior to 9.6.0-alpha.13 and 8.6.39 are affected by CVE-2026-32269.
What type of software vulnerability is CVE-2026-32269?
CVE-2026-32269 is an authentication vulnerability within the OAuth2 adapter of Parse Server.