Vulnerability · CVE-2026-27804
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js.
Published Feb 26, 2026 · catalog updated Jun 17, 2026 · Parse Server is an
Check if you run it
No confirmed exploitation is on record for CVE-2026-27804. EPSS is 0.24%. Act only if a listed version of Parse Server is an is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Parse Server is an).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Critical9.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.24%
- Remediation
- Advisory link
- Affected products
- cpe parseplatform/parse-server
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 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 algorithm instead of trusting the JWT header, and replaces the Google adapter's custom key fetcher with which rejects unknown key IDs. As a workaround, dsable Google authentication until upgrading is possible.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe parseplatform/parse-server9.3.1
How to fix CVE-2026-27804
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-27804. EPSS is 0.24%. Act only if a listed version of Parse Server is an is installed.
Which versions are affected?
Compare what you have installed with 9.3.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-327: Use of a Broken or Risky Cryptographic Algorithm; CWE-345: Insufficient Verification of Data Authenticity. EPSS 0.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Feb 26, 2026 · NIST NVD
Detected
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 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
Jun 17, 2026 · NIST NVD
Updated
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 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
Sources
- CVE.orgVulnerability recordCVE-2026-27804
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-27804
30-day exploitation probability 0.2%
first.org - NIST NVDVulnerability recordCVE-2026-27804
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 to log in as any user linked to a Google accou
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.