PT-2026-30320 · Npm · Parse Server

Published 2026-04-04 · Updated 2026-04-04 · CVE-2026-35200

OSV

CVSS v4.0

2.1

Low

AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

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.

Fix

Weakness Enumeration

CWE-436

Related Identifiers

CVE-2026-35200

GHSA-VR5F-2R24-W5HC

Affected Products

Parse Server

References · 5

• https://osv.dev/vulnerability/GHSA-vr5f-2r24-w5hc · Vendor Advisory
• https://github.com/parse-community/parse-server · Note
• https://github.com/parse-community/parse-server/pull/10384 · Note
• https://github.com/parse-community/parse-server/pull/10383 · Note
• https://github.com/parse-community/parse-server/security/advisories/GHSA-vr5f-2r24-w5hc · Note