CVE-2026-30949: Parse Server is missing audience validation in Keycloak authentication adapter
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
Other sources
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.5 and 8.6.18, 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. This vulnerability is fixed in 9.5.2-alpha.5 and 8.6.18.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-30949?
CVE-2026-30949 has not been assigned a Common Vulnerability Scoring System (CVSS) score, but it poses security risks related to unauthorized access.
How do I fix CVE-2026-30949?
To fix CVE-2026-30949, update Parse Server to version 9.5.2-alpha.5 or 8.6.18 or later.
What vulnerabilities are introduced by CVE-2026-30949?
CVE-2026-30949 allows for possible unauthorized access due to missing audience validation in the Keycloak authentication adapter.
Which versions of Parse Server are affected by CVE-2026-30949?
CVE-2026-30949 affects Parse Server versions prior to 9.5.2-alpha.5 and 8.6.18.
Where can I find more information about CVE-2026-30949?
For more information about CVE-2026-30949, visit the advisories section of the Parse Server GitHub repository.