CVE-2026-35200 json
Parse Server has a file upload Content-Type override via extension mismatch
published 2026-04-04 7 mo ago modified 2026-09-10 59 d ago also BIT-parse-2026-35200 , EUVD-2026-19473 , GHSA-vr5f-2r24-w5hc
- cvss
- 5.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm parse-server 8.6.73, 9.7.1-alpha.4
- bitnami parse 8.6.73, 9.7.1
- parseplatform parse-server 8.6.73, 9.7.1-alpha.4
- parseplatform parse_server 8.6.73, 9.7.1-alpha.4
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N |
| CNA | 4.0 | 2.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| OSV | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | parse-server | >=9.0.0, <9.7.1-alpha.4 <8.6.73 |
9.7.1-alpha.4 8.6.73 |
| bitnami | parse | <8.6.73 >=9.0.0, <9.7.1 |
8.6.73 9.7.1 |
Affected products
- parse-community parse-server
Classification
- Weakness
-
- CWE-436 Interpretation Conflict
References
-
github.com
/parse-community/parse-server/pull/10383
web, issue-tracking, patch
-
github.com
/parse-community/parse-server/pull/10384
web, issue-tracking, patch
-
github.com
/parse-community/parse-server/security/advisories/GHSA-vr5f-2r24-w5hc
web, mitigation, patch, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-35200
advisory, web
-
github.com
/parse-community/parse-server
package
Sources
- CVE List CVE-2026-35200
- GitHub Advisory GHSA-vr5f-2r24-w5hc
- NVD CVE-2026-35200
- OSV BIT-parse-2026-35200
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.