Vulnerability Description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 8.6.73 and 9.7.1-alpha.4, 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. This vulnerability is fixed in 8.6.73 and 9.7.1-alpha.4.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Parseplatform | Parse-Server | < 8.6.73 |
Related Weaknesses (CWE)
References
- https://github.com/parse-community/parse-server/pull/10383Issue TrackingPatch
- https://github.com/parse-community/parse-server/pull/10384Issue TrackingPatch
- https://github.com/parse-community/parse-server/security/advisories/GHSA-vr5f-2rMitigationPatchVendor Advisory
FAQ
What is CVE-2026-35200?
CVE-2026-35200 is a vulnerability with a CVSS score of 5.4 (MEDIUM). Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 8.6.73 and 9.7.1-alpha.4, a file can be uploaded with a filename extension that passes ...
How severe is CVE-2026-35200?
CVE-2026-35200 has been rated MEDIUM with a CVSS base score of 5.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-35200?
Check the references section above for vendor advisories and patch information. Affected products include: Parseplatform Parse-Server.