All vulnerabilities

Servers and applications

CVE-2026-55778

Stored XSS via non-standard file extension bypassing file upload extension blocklist

Severity
Low 2.1
Published
16 Jun 2026
Last changed
17 Jun 2026
Added to UpHeron
1 Nov 2026
Fixed in
8.6.81, 9.9.1-alpha.11
Exploit chance
0.6% in the next 30 daysHigher than 46% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Unrestricted file upload (CWE-434)
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
Also known as
GHSA-v8x7-r927-cc93
Sources
Project advisories (GitHub)

Description

Parse Server's default fileUpload.fileExtensions blocklist is intended to prevent uploading files that browsers render as active content (such as HTML and SVG), which can be used to perform stored cross-site scripting (XSS) attacks against other users. The blocklist could be bypassed by uploading a file whose extension is not an exact match of a blocked extension (for example a non-standard or compound extension) together with a dangerous content type. On storage adapters that persist and serve the uploaded content type (such as S3 and GCS), the file is then served with the attacker-supplied content type, enabling stored XSS against users who open the file URL.

This affects the default configuration, in which authenticated users are allowed to upload files. The default GridFS/filesystem adapter sets the X-Content-Type-Options: nosniff response header, which mitigates browser rendering on that adapter, but the upload restriction itself is still bypassed.

From parse-community/parse-server's security advisory. Shortened; the full text is there.

Workarounds

Configure fileUpload.fileExtensions as a strict allowlist of only the file extensions your application needs (for example ["^(png|jpe?g|gif|pdf)$"]) instead of relying on the default blocklist. Additionally, serve uploaded files from a separate domain than the application, so that any executed content is isolated from the application's origin.

Workarounds as given by parse-community/parse-server's security advisory.

Affected software

SoftwareAffected versions
Parse ServerServers and applications · github:parse-community/parse-server
  • Every version before 8.6.81
  • From 9.0.0 before 9.9.1-alpha.11

About Parse Server

Parse Server for Node.js / Express

From its GitHub repository.
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

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-55778
  • GitHub Advisory Database https://github.com/advisories/GHSA-v8x7-r927-cc93
  • github.com https://github.com/parse-community/parse-server/security/advisories/GHSA-v8x7-r927-cc93