BIT-parse-2026-55778: Parse Server: Stored XSS via non-standard file extension bypassing file upload extension blocklist

Published Jul 8, 2026
·
Updated

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.9.1-alpha.11 and 8.6.81, the default fileUpload.fileExtensions blocklist could be bypassed by uploading a file with a non-standard or compound extension and dangerous content type, allowing storage adapters such as S3 and GCS to serve attacker-supplied active content and enable stored cross-site scripting. This issue is fixed in versions 9.9.1-alpha.11 and 8.6.81.

Affected Software

1 affected component
Parse Platform Parse Server<9.9.1-alpha.11, <8.6.81

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 9.9.1-alpha.11
  2. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 8.6.81

Event History

Jul 8, 2026
CVE Published
via OSV·08:50 PM
Data Sourced
via OSV·08:50 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Parse Server deployments before 9.9.1-alpha.11 and 8.6.81 are affected when they rely on the default fileUpload.fileExtensions blocklist and use storage adapters such as S3 or GCS that can serve uploaded content.

2

What does an attacker need to exploit the vulnerability?

The attacker needs low-level privileges and user interaction. They must be able to upload a file using a non-standard or compound extension with a dangerous content type, then cause a user to load the stored active content.

3

Are default configurations affected?

Yes. The issue specifically affects the default fileUpload.fileExtensions blocklist, which can be bypassed with non-standard or compound file extensions.

4

What should be done if upgrading is not immediately possible?

The provided information does not specify a workaround. Prioritize upgrading to 9.9.1-alpha.11 or 8.6.81, and review uploaded files that may have non-standard or compound extensions and dangerous content types.

5

How can I determine whether my deployment may already be affected?

Check whether the Parse Server version is earlier than 9.9.1-alpha.11 or 8.6.81, whether the default fileUpload.fileExtensions blocklist is in use, and whether uploads are served through S3 or GCS. Review stored uploads for files with non-standard or compound extensions that may contain active content.

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