Servers and applications
GHSA-r899-h629-j84r
Stored XSS via malformed Content-Type bypassing file upload extension blocklist
- Severity
- Low 2.1
- Published
- 25 Jun 2026
- Last changed
- 25 Jun 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 8.6.84, 9.10.0-alpha.2
- Attack
- Over the network · Only under certain conditions · Needs a user account · Needs someone to view a page or file
- Attacker can
- Change some data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N- Sources
- Project advisories (GitHub)
Description
Parse Server's file upload validation uses the fileUpload.fileExtensions option (enabled by default with a blocklist) to reject files that browsers may render as active content, mitigating stored cross-site scripting (XSS). When an uploaded file's extension is not recognized by the mime package, Parse Server preserves the client-supplied Content-Type and passes it to the storage adapter. A malformed Content-Type that is not a valid type/subtype media type — for example image (no subtype), image/ (empty subtype), or image//svg+xml (invalid token) — bypassed the blocklist and was stored unchanged. On storage adapters that persist and serve the uploaded Content-Type (such as Amazon S3, Google Cloud Storage, or Azure Blob Storage), a browser cannot parse the malformed Content-Type and falls back to MIME-sniffing the file content; a file whose body begins with HTML markup is then rendered as HTML, executing any embedded script in the application's origin.
Workarounds
Configure fileUpload.fileExtensions as a strict allowlist of only the extensions the application needs (for example ["^(png|jpe?g|gif|pdf)$"]). Additionally, serve uploaded files from a domain separate from the application so that any rendered content is isolated from the application's origin, and configure the storage/CDN layer to send X-Content-Type-Options: nosniff.
Affected software
| Software | Affected versions |
|---|---|
Parse ServerServers and applications · github:parse-community/parse-server |
|
About Parse Server
Parse Server for Node.js / Express
- Weekly downloads (npm)
- 54,531npm, 15 Nov 2026
- Docker Hub pulls
- 4,250,088Docker Hub, 15 Nov 2026
- GitHub stars
- 21,396GitHub, 15 Nov 2026
- Forks
- 4,811GitHub, 15 Nov 2026
- Latest release
- 8.6.123GitHub, 15 Nov 2026
- Released
- 9 Nov 2026GitHub
- License
- Apache-2.0GitHub
- First published on GitHub
- 28 Jan 2016GitHub
Source code Website Docker image Package
Vulnerabilities in Parse Server
- In our list
- 184
- Published in the last 12 months
- 156
- Critical, last 12 months
- 14
- High, last 12 months
- 52
- Known exploited
- 0
- GHSA-9v83-v857-2xf8Query and LiveQuery subscription constraints disclose the auth data and session token of a userHigh 8.2 19 Nov 2026
- CVE-2026-130671Parse Server before 8.6.119 and 9.x before 9.10.8-alpha.3 LiveQuery Missing AuthorizationMedium 6.3 18 Nov 2026
- GHSA-f92h-3w9f-hg55LiveQuery discloses MFA secrets and auth data that an auth adapter hides to a subscription of the user itselfMedium 5.9 17 Nov 2026
- GHSA-43rg-r2xr-q686Login with auth data discloses MFA secrets and user fields that the user is not allowed to readMedium 5.9 14 Nov 2026
- CVE-2026-126392Parse Server 9.10.6-alpha.1 before 9.10.8-alpha.1 Information Disclosure via Dot Notation UpdateLow 2.3 13 Nov 2026
- GHSA-f6wh-8wcf-xfv8LiveQuery subscription with a large list constraint can block the event loopHigh 8.2 11 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-r899-h629-j84r
- github.com https://github.com/parse-community/parse-server/security/advisories/GHSA-r899-h629-j84r