Vulnerability Description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.9. and 8.6.22, the OAuth2 authentication adapter, when configured without the useridField option, only verifies that a token is active via the provider's token introspection endpoint, but does not verify that the token belongs to the user identified by authData.id. An attacker with any valid OAuth2 token from the same provider can authenticate as any other user. This affects any Parse Server deployment that uses the generic OAuth2 authentication adapter (configured with oauth2: true) without setting the useridField option. This vulnerability is fixed in 9.5.2-alpha.9. and 8.6.22.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Parseplatform | Parse-Server | < 8.6.22 |
Related Weaknesses (CWE)
References
- https://github.com/parse-community/parse-server/releases/tag/8.6.22ProductRelease Notes
- https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.9ProductRelease Notes
- https://github.com/parse-community/parse-server/security/advisories/GHSA-fr88-w3PatchVendor Advisory
FAQ
What is CVE-2026-30967?
CVE-2026-30967 is a vulnerability with a CVSS score of 8.8 (HIGH). Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.9. and 8.6.22, the OAuth2 authentication adapter, when configured without t...
How severe is CVE-2026-30967?
CVE-2026-30967 has been rated HIGH with a CVSS base score of 8.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-30967?
Check the references section above for vendor advisories and patch information. Affected products include: Parseplatform Parse-Server.