Interpretation Conflict Affecting parse-server package, versions <8.6.73>=9.0.0-alpha.1 <9.7.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 applications- Snyk IDSNYK-JS-PARSESERVER-15906332
- published5 Apr 2026
- disclosed4 Apr 2026
- creditoffset
Introduced: 4 Apr 2026
CVE-2026-35200 (opens in a new tab)How to fix?
Upgrade parse-server to version 8.6.73, 9.7.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 Interpretation Conflict via the file upload process. An attacker can cause files to be served with an unintended Content-Type by uploading files with a mismatched extension and Content-Type header, potentially leading to files being interpreted incorrectly by clients or browsers. This is only exploitable if the storage adapter or CDN serves files using the stored Content-Type rather than deriving it from the filename extension.
Workaround
This vulnerability can be mitigated by configuring the storage adapter or CDN to derive the Content-Type from the filename extension instead of using the stored Content-Type.