Vulnerability · Published Apr 6, 2026 · Assigned by GitHub_M

CVE-2026-35200Parse Server has a file upload Content-Type override via extension mismatch

Low 2.1

In plain English

A low-severity security flaw in parse-server from parse-community. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)2.1Low
Exploit odds (30 days)0.2%top 93.8% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npmparse-server9.7.1-alpha.4GHSA-vr5f-2r24-w5hc
npmparse-server8.6.73GHSA-vr5f-2r24-w5hc

Affected products (as reported)

VendorProductVersions
parse-community parse-server >= 9.0.0, < 9.7.1-alpha.4< 8.6.73

Weakness: CWE-436 · Vector: 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

References