Parse Server missing audience validation in Keycloak authentication adapter
GHSA-48mh-j4p5-7j9v · BIT-parse-2026-30949 · CVE-2026-30949
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
Impact
The Keycloak authentication adapter does not validate the azp (authorized party) claim of Keycloak access tokens against the configured client-id. A valid access token issued by the same Keycloak realm for a different client application can be used to authenticate as any user on the Parse Server that uses the Keycloak adapter. This enables cross-application account takeover in multi-client Keycloak realms.
All Parse Server deployments that use the Keycloak authentication adapter with a Keycloak realm that has multiple client applications are affected.
Patches
The fix replaces the userinfo HTTP call with local JWT verification and enforces azp claim validation against the configured client-id.
Workarounds
None.
References
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-48mh-j4p5-7j9v
- Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.5
- Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.18
References
- WEB https://github.com/parse-community/parse-server/security/advisories/GHSA-48mh-j4p5-7j9v
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-30949
- PACKAGE https://github.com/parse-community/parse-server
- WEB https://github.com/parse-community/parse-server/releases/tag/8.6.18
- WEB https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.5
Ready to move
Start Securing
Free, no credit card | First findings in minutes