CVE-2026-55778: parse-server Cross-Site Scripting Vulnerability

LOW
Advisory Identifier: GHSA-v8x7-r927-cc93
CWE-434
Published
Advisory Summary

CVE-2026-55778 is a LOW cross-site scripting vulnerability (CWE-434: Unrestricted Upload of File with Dangerous Type) affecting parse-server libraries in the npm ecosystem. The issue involves stored xss via non-standard file extension bypassing file upload extension blocklist. Remediation is available by upgrading affected packages to version 9.9.1-alpha.11, 8.6.81.

CVE-2026-55778 at a Glance

CVE Identifier CVE-2026-55778
GHSA Identifier GHSA-v8x7-r927-cc93
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-434: Unrestricted Upload of File with Dangerous Type
Affected Product parse-server
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-55778

To remediate this vulnerability, upgrade all affected parse-server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

parse-server fixed: 9.9.1-alpha.11
npm install parse-server@9.9.1-alpha.11
parse-server fixed: 8.6.81
npm install parse-server@8.6.81
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls parse-server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-55778, inspect your project dependencies using npm:

npm ls parse-server

Analyze the terminal output to locate any version of parse-server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.9.1-alpha.11), your application is affected.

Note: The npm ls parse-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-434: Unrestricted Upload of File with Dangerous Type, where the product allows the upload or transfer of dangerous file types that are automatically processed within its environment. In parse-server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact 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. This is an incomplete-fix follow-up of GHSA-vr5f-2r24-w5hc and GHSA-7wqv-xjf3-x35v. ### Patches The file upload extension validation now also evaluates the request content type against the configured blocklist whenever the filename's extension is not a recognized type. As a result, a dangerous content type can no longer be preserved by uploading a file with a non-standard extension, and such uploads are rejected. ### 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.

CVE-2026-55778 Affected parse-server Versions

2 component(s)
Fixed Versions:
9.9.1-alpha.118.6.81
Product / Package Ecosystem Affected Versions Fixed Version
parse-server
npm
≥ 9.0.0
< 9.9.1-alpha.11
9.9.1-alpha.11
parse-server
npm
< 8.6.81
8.6.81

References

Frequently Asked Questions

What is CVE-2026-55778?
CVE-2026-55778 is a security vulnerability in parse-server involving Stored XSS via non-standard file extension bypassing file upload extension blocklist under CWE-434: Unrestricted Upload of File with Dangerous Type.
Which parse-server versions are affected?
Affected versions include releases prior to 9.9.1-alpha.11, 8.6.81 across affected packages: parse-server.
What version fixes CVE-2026-55778?
Upgrading to 9.9.1-alpha.11, 8.6.81 (or the latest patched release for your respective branch) resolves the vulnerability.
Is parse-server affected?
Yes, parse-server is affected in releases prior to 9.9.1-alpha.11, 8.6.81. Upgrade your dependency to 9.9.1-alpha.11, 8.6.81 or later.
What CWE is associated with CVE-2026-55778?
CVE-2026-55778 is classified under CWE-434: Unrestricted Upload of File with Dangerous Type (The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.).
How can I check npm dependencies for CVE-2026-55778?
Run the dependency tree command: 'npm ls parse-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v8x7-r927-cc93",
  "modified" : "2026-06-19T19:36:36Z",
  "published" : "2026-06-19T19:36:36Z",
  "aliases" : [ "CVE-2026-55778" ],
  "summary" : "parse-server: Stored XSS via non-standard file extension bypassing file upload extension blocklist",
  "details" : "### Impact\n\nParse 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.\n\nThis 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. This is an incomplete-fix follow-up of GHSA-vr5f-2r24-w5hc and GHSA-7wqv-xjf3-x35v.\n\n### Patches\n\nThe file upload extension validation now also evaluates the request content type against the configured blocklist whenever the filename's extension is not a recognized type. As a result, a dangerous content type can no longer be preserved by uploading a file with a non-standard extension, and such uploads are rejected.\n\n### Workarounds\n\nConfigure `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.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.0.0"
      }, {
        "fixed" : "9.9.1-alpha.11"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.81"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 8.6.80"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-v8x7-r927-cc93"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10505"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10506"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-434" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T19:36:36Z",
    "nvd_published_at" : null
  }
}