Advisory

GHSA-48mh-j4p5-7j9v

Also known as: BIT-parse-2026-30949, CVE-2026-30949

Summary

Parse Server missing audience validation in Keycloak authentication adapter

Details

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

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-03-11 00:17 UTC
Modified
2026-03-14 03:41 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0, fixed 9.5.2-alpha.5 (semver)

Fixed versions

9.5.2-alpha.5

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.18 (semver)

Fixed versions

8.6.18

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences