CVE-2026-27804: Parse Server: Account takeover via JWT algorithm confusion in Google auth adapter

Published Feb 25, 2026
·
Updated

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

Other sources

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.

NVD

Affected Software

7 affected componentsFixes available
npm/parse-server<=8.6.2
8.6.3
npm/parse-server>=9.0.0<=9.3.1-alpha.3
9.3.1-alpha.4
parseplatform Parse-server Node.js<8.6.3
parseplatform Parse-server Node.js>=9.0.0<9.3.1
parseplatform Parse-server Node.js=9.3.1-alpha1
parseplatform Parse-server Node.js=9.3.1-alpha2
parseplatform Parse-server Node.js=9.3.1-alpha3

Event History

Feb 25, 2026
Advisory Published
via GitHub·11:00 PM
Data Sourced
via GitHub·11:00 PM
DescriptionWeaknessAffected Software
CVE Published
via MITRE·11:48 PM
Data Sourced
via MITRE·11:48 PM
DescriptionWeakness
Feb 26, 2026
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:16 AM
RemedyAffected Software
Mar 23, 58145
Event
via FIRST·12:50 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-27804?

CVE-2026-27804 is considered a critical vulnerability due to its potential for account takeover.

2

How do I fix CVE-2026-27804?

To fix CVE-2026-27804, upgrade to Parse Server version 8.6.3 or 9.3.1-alpha.4 or later.

3

Who is affected by CVE-2026-27804?

CVE-2026-27804 affects deployments of Parse Server using Google authentication versions up to 8.6.2 and between 9.0.0 and 9.3.1-alpha.3.

4

What type of attack is associated with CVE-2026-27804?

CVE-2026-27804 is associated with an account takeover attack via JWT algorithm confusion.

5

Can CVE-2026-27804 be exploited without authentication?

Yes, CVE-2026-27804 can be exploited by an unauthenticated attacker to log in as any user linked to a Google account.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203