Parse Server vulnerable to stored XSS via malformed Content-Type bypassing file upload extension blocklist
Affects parse-serverSource GCVE Database
Not known to be exploited · CVSS 2.1 Low : upgrade to 9.10.0-alpha.2 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.10.0-alpha.2, 8.6.84
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade parse-server to 9.10.0-alpha.2; parse-server to 8.6.84.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmparse-server | Affected
| Fixed in
|
| npmparse-server | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and should be applied to upgrade Parse Server to version 9.10.0-alpha.2 or later, or 8.6.84 or later, which validate that client-supplied Content-Type headers are well-formed and reject malformed values. As a workaround, configure fileUpload.fileExtensions as a strict allowlist of only necessary extensions (e.g., ["^(png|jpe?g|gif|pdf)$"]). Additionally, serve uploaded files from a domain separate from the application to isolate any rendered content, and configure the storage or CDN layer to send the X-Content-Type-Options: nosniff header to prevent MIME-sniffing by browsers.
Description
Parse Server versions prior to 9.10.0-alpha.2 and 8.6.84 are vulnerable to a stored cross-site scripting (XSS) issue via malformed Content-Type headers in file uploads. The vulnerability arises because malformed Content-Type values that do not conform to the type/subtype format can bypass the file extension blocklist and be stored unchanged. When served from storage adapters that preserve the Content-Type header (e.g., Amazon S3, Google Cloud Storage, Azure Blob Storage), browsers may MIME-sniff the file content and execute embedded scripts, leading to stored XSS. The default GridFS adapter is not affected due to recomputing Content-Type and using X-Content-Type-Options: nosniff. Patches are available that validate Content-Type headers for well-formedness and reject malformed values.
References
- github.com/parse-community/parse-server/security/advisories/GHSA-r899-h629-j84r (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-61448 (opens in a new tab)
- github.com/parse-community/parse-server (opens in a new tab)
- vulncheck.com/advisories/parse-server-stored-xss-via-malformed-content-type (opens in a new tab)