parse-server
Affected
- introduced
9.0.0, fixed9.5.2-alpha.5(semver)
Fixed versions
9.5.2-alpha.5
Fix
- Fixed version
9.5.2-alpha.5npm install [email protected]
Advisory
Also known as: BIT-parse-2026-30949, CVE-2026-30949
Parse Server 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
High Basis: The source's own band: HIGH
9.0.0, fixed 9.5.2-alpha.5 (semver)9.5.2-alpha.5
9.5.2-alpha.5npm install [email protected]0, fixed 8.6.18 (semver)8.6.18
8.6.18npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0