Advisory

GHSA-vr5f-2r24-w5hc

Also known as: BIT-parse-2026-35200, CVE-2026-35200

Summary

Parse Server: File upload Content-Type override via extension mismatch

Details

Impact

A file can be uploaded with a filename extension that passes the file extension allowlist (e.g., .txt) but with a Content-Type header that differs from the extension (e.g., text/html). The Content-Type is passed to the storage adapter without consistency validation. Storage adapters that store and serve the provided Content-Type (such as S3 or GCS) serve the file with the mismatched Content-Type. The default GridFS adapter is not affected because it derives Content-Type from the filename at serving time.

Patches

The file upload now derives the Content-Type from the filename extension, overriding any user-provided Content-Type when the file has an extension.

Workarounds

Configure the storage adapter or CDN to derive Content-Type from the filename extension instead of using the stored Content-Type.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-04-04 04:22 UTC
Modified
2026-04-08 15:41 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0, fixed 9.7.1-alpha.4 (semver)

Fixed versions

9.7.1-alpha.4

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.73 (semver)

Fixed versions

8.6.73

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences