CVE-2026-32269

Parse Server OAuth2 adapter app ID validation sends wrong token to introspection endpoint

CVSS 6.3 MEDIUMEPSS 0.3%CWE-683

Vexday Risk Score

13Low

SSVC decision (CISA)

Track

No exploitation signal → monitor

CVSS 6.3EPSS 0.3%KEV nãoPoC —Nuclei —Metasploit —Patch —

Lifecycle

12 Mar 2026Published on NVD

Recommendation: Monitor — no exploitation signal at the moment.

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.

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Affected products

parse-community · parse-server

Want to know if your infrastructure is exposed to this?

Talk to TrueHacking →

References

https://github.com/parse-community/parse-server/releases/tag/8.6.39 https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.13 https://github.com/parse-community/parse-server/security/advisories/GHSA-69xg-f649-w5g2