Advisory

GHSA-4q3h-vp4r-prv2

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

Summary

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

Details

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

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2026-02-25 23:00 UTC
Modified
2026-03-02 12:17 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0, fixed 9.3.1-alpha.4 (semver)

Fixed versions

9.3.1-alpha.4

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.3 (semver)

Fixed versions

8.6.3

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