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.
References
| Link | Resource |
|---|---|
| https://github.com/parse-community/parse-server/pull/10383 | Issue Tracking Patch |
| https://github.com/parse-community/parse-server/pull/10384 | Issue Tracking Patch |
| https://github.com/parse-community/parse-server/security/advisories/GHSA-vr5f-2r24-w5hc | Mitigation Patch Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-04-06 20:16
Updated : 2026-07-24 21:10
NVD link : CVE-2026-35200
Mitre link : CVE-2026-35200
CVE.ORG link : CVE-2026-35200
JSON object : View
Products Affected
parseplatform
- parse-server
CWE
CWE-436
Interpretation Conflict
