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.
The fix replaces the userinfo HTTP call with local JWT verification and enforces azp claim validation against the configured client-id.
None.
{
"severity": "HIGH",
"cwe_ids": [
"CWE-287"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-11T00:17:53Z",
"nvd_published_at": "2026-03-10T21:16:47Z"
}