Summary
Workarounds
Configure the storage adapter or CDN to derive Content-Type from the filename extension instead of using the stored Content-Type.
Impact
A file can be uploaded with a filename extension that passes the file extension allowlist (e.g., .txt) but with a Content-Type header that differs from the extension (e.g., text/html). The Content-Type is passed to the storage adapter without consistency validation. Storage adapters that store and serve the provided Content-Type (such as S3 or GCS) serve the file with the mismatched Content-Type. The default GridFS adapter is not affected because it derives Content-Type from the filename at serving time.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
The file upload now derives the Content-Type from the filename extension, overriding any user-provided Content-Type when the file has an extension.
Frequently Asked Questions
- What is CVE-2026-35200? CVE-2026-35200 is a low-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.7.1-alpha.4. It is fixed in 9.7.1-alpha.4, 8.6.73.
- Which versions of parse-server are affected by CVE-2026-35200? parse-server (npm) versions >= 9.0.0, < 9.7.1-alpha.4 is affected.
- Is there a fix for CVE-2026-35200? Yes. CVE-2026-35200 is fixed in 9.7.1-alpha.4, 8.6.73. Upgrade to this version or later.
- Is CVE-2026-35200 exploitable, and should I be worried? Whether CVE-2026-35200 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-35200 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-35200?
- Upgrade
parse-serverto 9.7.1-alpha.4 or later - Upgrade
parse-serverto 8.6.73 or later
- Upgrade