GHSA-4q3h-vp4r-prv2

Parse Server: Account takeover via JWT algorithm confusion in Google auth adapter

At a glance

Published
Updated
CVE
CVE-2026-27804
Aliases
BIT-parse-2026-27804
CVSS_V4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Description

### Impact An unauthenticated attacker can forge a Google authentication token with `alg: "none"` to log in as any user linked to a Google account, without knowing their credentials. All deployments with Google authentication enabled are affected. ### Patches The fix hardcodes the expected `RS256` algorithm instead of trusting the JWT header, and replaces the Google adapter's custom key fetcher with `jwks-rsa` which rejects unknown key IDs. ### Workarounds Disable Google authentication until you can upgrade. ### References - GitHub advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-4q3h-vp4r-prv2 - Fixed in Parse Server 9.3.1-alpha.4: https://github.com/parse-community/parse-server/releases/tag/9.3.1-alpha.4 - Fixed in Parse Server 8.6.3: https://github.com/parse-community/parse-server/releases/tag/8.6.3

Affected packages

PackageVersions
npm · parse-serverintroduced 9.0.0, fixed 9.3.1-alpha.4
npm · parse-serverintroduced 0, fixed 8.6.3

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database