Use of a Broken or Risky Cryptographic Algorithm Affecting parse-server package, versions <8.6.3>=9.0.0-alpha.1 <9.3.1-alpha.4
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-PARSESERVER-15357994
- published26 Feb 2026
- disclosed26 Feb 2026
- creditsebastianosrt
Introduced: 26 Feb 2026
CVE-2026-27804 (opens in a new tab)How to fix?
Upgrade parse-server to version 8.6.3, 9.3.1-alpha.4 or higher.
Overview
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js.
Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm via the Google authentication. An attacker can gain unauthorized access to any user account linked with Google authentication by forging a JWT token with alg set to "none". This is only exploitable if Google authentication is enabled.
Workaround
This vulnerability can be mitigated by disabling Google authentication until upgrading is possible.