parse-server
Affected
- introduced
9.0.0-alpha.1, fixed9.5.0-alpha.11(semver)
Fixed versions
9.5.0-alpha.11
Fix
- Fixed version
9.5.0-alpha.11npm install [email protected]
Advisory
Also known as: BIT-parse-2026-30863, CVE-2026-30863
Parse Server: JWT audience validation bypass in Google, Apple, and Facebook authentication adapters
Impact
The Google, Apple, and Facebook authentication adapters use JWT verification to validate identity tokens. When the adapter's audience configuration option is not set (clientId for Google/Apple, appIds for Facebook), JWT verification silently skips audience claim validation. This allows an attacker to use a validly signed JWT issued for a different application to authenticate as any user on the target Parse Server.
clientId. The adapters accepted this as valid and simply skipped audience validation.appIds only for Standard Login (Graph API), but the Limited Login JWT path never passed appIds as the audience to JWT verification.Patches
The fix enforces clientId (Google/Apple) and appIds (Facebook) as mandatory and passes them to JWT verification for audience validation. While this is technically a breaking change for servers that omit these options, it is not a breaking change as per documentation — all three options are documented as required configuration.
Workarounds
clientId is set in the adapter configuration. When set, JWT verification correctly validates the audience claim even on unpatched versions.appIds to JWT audience validation, so the only mitigation is to upgrade.References
Critical Basis: The source's own band: CRITICAL
9.0.0-alpha.1, fixed 9.5.0-alpha.11 (semver)9.5.0-alpha.11
9.5.0-alpha.11npm install [email protected]0, fixed 8.6.10 (semver)8.6.10
8.6.10npm 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