BIT-parse-2026-55778: Parse Server: Stored XSS via non-standard file extension bypassing file upload extension blocklist
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Parse Serverto a version that resolves this vulnerability.Fixed in 9.9.1-alpha.11 - Upgrade
Upgrade
Parse Serverto a version that resolves this vulnerability.Fixed in 8.6.81
Event History
Frequently Asked Questions
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.
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.
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.
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.
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.