CVE-2026-61448: Parse Server vulnerable to stored XSS via malformed Content-Type bypassing file upload extension blocklist

Published Jul 11, 2026
·
Updated

Impact

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. This allows a user permitted to upload files to store content that executes as script against other users who open the file URL. The default GridFS storage adapter is not affected, as it recomputes the Content-Type from the filename and serves files with X-Content-Type-Options: nosniff.

Patches

The file upload handler now validates that the client-supplied Content-Type is a well-formed media type (type/subtype with non-empty tokens per RFC 9110 §5.6.2) whenever the filename extension is not recognized by mime. Malformed values are rejected instead of being stored, while well-formed types — including custom or vendor types that the mime package does not recognize — continue to be accepted; only blocklisted subtypes are rejected.

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.

References

- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-r899-h629-j84r - Fix Parse Server 9: https://github.com/parse-community/parse-server/pull/10521 - Fix Parse Server 8: https://github.com/parse-community/parse-server/pull/10523

Other sources

Parse Server is affected by a stored cross-site scripting (XSS) vulnerability in versions >= 9.0.0, < 9.10.0-alpha.2 and <= 8.6.83. When an uploaded file's extension is not recognized by the mime package, Parse Server preserves the client-supplied Content-Type. A malformed Content-Type that is not a valid type/subtype media type (e.g., 'image', 'image/', or 'image//svg+xml') bypasses the fileUpload.fileExtensions blocklist and is 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 value and falls back to MIME-sniffing; a file whose body begins with HTML is rendered as HTML, executing embedded script in the application's origin against other users who open the file URL. The default GridFS storage adapter is not affected. Fixed in 9.10.0-alpha.2 and 8.6.84.

— MITRE

Affected Software

5 affected componentsFixes available
Parse Parse Server>=9.0.0<9.10.0-alpha.2
Parse Parse Server<=8.6.83
npm/parse-server<=8.6.83
8.6.84
npm/parse-server>=9.0.0<9.10.0-alpha.2
9.10.0-alpha.2
npm/parse-server<8.6.84
8.6.84

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/parse-server to a version that resolves this vulnerability.

    Fixed in 8.6.84
  2. Upgrade

    Upgrade npm/parse-server to a version that resolves this vulnerability.

    Fixed in 9.10.0-alpha.2
  3. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 9.10.0-alpha.2
  4. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 8.6.84
  5. Configuration

    Configure fileUpload.fileExtensions as a strict allowlist containing only the extensions required by the application.

    Parse Server file upload handler fileUpload.fileExtensions = ["^(png|jpe?g|gif|pdf)$"]
  6. Compensating control

    Serve uploaded files from a domain separate from the application so rendered content is isolated from the application's origin.

  7. Compensating control

    Configure the storage or CDN layer to send the X-Content-Type-Options: nosniff response header.

Event History

Jul 11, 2026
CVE Published
via MITRE·01:01 PM
Data Sourced
via MITRE·01:01 PM
DescriptionWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeakness
Oct 29, 2026
Advisory Published
via GitHub·04:33 PM
Data Sourced
via GitHub·04:33 PM
DescriptionWeaknessAffected Software
Data Sourced
via OSV·04:33 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-61448?

The severity of CVE-2026-61448 is rated low, with a CVSS score of 4.0.

2

How do I fix CVE-2026-61448?

To fix CVE-2026-61448, upgrade Parse Server to version 9.10.0-alpha.2 or higher.

3

What types of vulnerabilities does CVE-2026-61448 involve?

CVE-2026-61448 involves stored cross-site scripting (XSS) and malicious file upload vulnerabilities.

4

Which versions of Parse Server are affected by CVE-2026-61448?

CVE-2026-61448 affects Parse Server versions greater than or equal to 9.0.0 and less than 9.10.0-alpha.2, as well as version 8.6.83.

5

What is the exploit mechanism for CVE-2026-61448?

The exploit mechanism for CVE-2026-61448 involves an uploaded file with an unrecognized extension, allowing the client-supplied Content-Type to be preserved.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203