Parse Server missing audience validation in Keycloak authentication adapter

Description

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.

Recommendation

Update the parse-server package to the latest compatible version. Followings are version details:

• Affected version(s): **< 8.6.18

  >= 9.0.0, < 9.5.2-alpha.5**

• Patched version(s): **8.6.18

  9.5.2-alpha.5**

References

• GHSA-48mh-j4p5-7j9v
• CVE-2026-30949
• CWE-287
• CAPEC-310
• OWASP 2021-A6
• OWASP 2021-A7

Related Issues

• Parse Server: JWT audience validation bypass in Google, Apple, and Facebook authentication adapters - CVE-2026-30863
• Parse Server OAuth2 authentication adapter account takeover via identity spoofing - CVE-2026-30967
• Parse Server OAuth2 adapter app ID validation sends wrong token to introspection endpoint - CVE-2026-32269
• Parse Server: Account takeover via operator injection in authentication data identifier - CVE-2026-32248

Tags:

npm

parse-server