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

LOW
Advisory Identifier: GHSA-7wqv-xjf3-x35v
CWE-434 CWE-79
Published
Advisory Summary

CVE-2026-53724 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 trailing-dot filename bypassing file upload extension blocklist. Remediation is available by upgrading affected packages to version 9.9.1-alpha.4, 8.6.79.

CVE-2026-53724 at a Glance

CVE Identifier CVE-2026-53724
GHSA Identifier GHSA-7wqv-xjf3-x35v
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-53724

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.4
npm install parse-server@9.9.1-alpha.4
parse-server fixed: 8.6.79
npm install parse-server@8.6.79
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-53724, 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.4), 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 & RFC 5280 Specification

Under RFC 5280 specifications for X.509 certificates, the Name Constraints extension defines a namespace within which all subsequent subject names in a certification path must be located. Constraints apply to various name forms including directory names, IP addresses, rfc822Name (email addresses), and uniformResourceIdentifier (URI) entries. Specifically, during certificate path validation, affected versions of parse-server failed to properly normalize or enforce boundary checks when domain names contained trailing dot (.) characters. Because domain names with a trailing dot signify fully qualified domain names (FQDNs), this omission allowed non-conforming certificates to be improperly validated as compliant with the defined name constraints.

Source Advisory Statement

### Impact The default file upload extension blocklist can be bypassed by appending a trailing dot to a filename whose extension would otherwise be blocked (e.g. `poc.svg.`). The trailing dot causes the extension parser to extract an empty string, which short-circuits the blocklist check, and the attacker-controlled Content-Type is forwarded to the storage adapter unchanged. Storage adapters that persist and serve the provided Content-Type (such as S3 or GCS) then serve the file with an active type such as `image/svg+xml`, enabling stored XSS when a victim opens the file URL. The default GridFS adapter is not affected because it sets `X-Content-Type-Options: nosniff` on responses. ### Patches A filename ending in a dot is now treated as extensionless. When the parser produces an empty extension, the request handler falls back to validating the Content-Type subtype against the configured extension blocklist, matching the path that already catches truly extensionless uploads with a dangerous Content-Type. This is a follow-up to the previous fix [GHSA-vr5f-2r24-w5hc](https://github.com/parse-community/parse-server/security/advisories/GHSA-vr5f-2r24-w5hc). ### Workarounds Configure the storage adapter or CDN to derive Content-Type from the filename extension instead of using the stored Content-Type, or replace the default blocklist with an explicit allowlist of needed file extensions.

CVE-2026-53724 Affected parse-server Versions

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

References

Frequently Asked Questions

What is CVE-2026-53724?
CVE-2026-53724 is a security vulnerability in parse-server involving Stored XSS via trailing-dot filename 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.4, 8.6.79 across affected packages: parse-server.
What version fixes CVE-2026-53724?
Upgrading to 9.9.1-alpha.4, 8.6.79 (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.4, 8.6.79. Upgrade your dependency to 9.9.1-alpha.4, 8.6.79 or later.
What CWE is associated with CVE-2026-53724?
CVE-2026-53724 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-53724?
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-7wqv-xjf3-x35v",
  "modified" : "2026-06-19T19:35:11Z",
  "published" : "2026-06-19T19:35:11Z",
  "aliases" : [ "CVE-2026-53724" ],
  "summary" : "parse-server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist",
  "details" : "### Impact\n\nThe default file upload extension blocklist can be bypassed by appending a trailing dot to a filename whose extension would otherwise be blocked (e.g. `poc.svg.`). The trailing dot causes the extension parser to extract an empty string, which short-circuits the blocklist check, and the attacker-controlled Content-Type is forwarded to the storage adapter unchanged. Storage adapters that persist and serve the provided Content-Type (such as S3 or GCS) then serve the file with an active type such as `image/svg+xml`, enabling stored XSS when a victim opens the file URL. The default GridFS adapter is not affected because it sets `X-Content-Type-Options: nosniff` on responses.\n\n### Patches\n\nA filename ending in a dot is now treated as extensionless. When the parser produces an empty extension, the request handler falls back to validating the Content-Type subtype against the configured extension blocklist, matching the path that already catches truly extensionless uploads with a dangerous Content-Type. This is a follow-up to the previous fix [GHSA-vr5f-2r24-w5hc](https://github.com/parse-community/parse-server/security/advisories/GHSA-vr5f-2r24-w5hc).\n\n### Workarounds\n\nConfigure the storage adapter or CDN to derive Content-Type from the filename extension instead of using the stored Content-Type, or replace the default blocklist with an explicit allowlist of needed file extensions.",
  "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.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.79"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 8.6.78"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-7wqv-xjf3-x35v"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-53724"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10489"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10490"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-434", "CWE-79" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T19:35:11Z",
    "nvd_published_at" : "2026-06-12T19:16:30Z"
  }
}