En bref
- CVE-2026-27804 est une vulnérabilité CRITIQUE (CVSS 9.1) touchant parse-server (parseplatform), parse-server.
- Probabilité d'exploitation dans les 30 prochains jours (EPSS) : 0.20%, plus élevée que 10.0% des vulnérabilités.
- Correctif : mettre à jour vers 9.3.1, 8.6.3, 9.3.1-alpha.4 ou plus récent.
| Package | Affected versions | Patched versions |
|---|
| parse-server | = 9.3.1≥ 9.0.0, < 9.3.1< 8.6.3
| 9.3.18.6.3
|
| parse-server npm | ≥ 9.0.0, < 9.3.1-alpha.4< 8.6.3
| 9.3.1-alpha.48.6.3
|
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
NVD description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.3 and 9.1.1-alpha.4, 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. The fix in versions 8.6.3 and 9.1.1-alpha.4 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. As a workaround, dsable Google authentication until upgrading is possible.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free