Skip to main content
VulnerabilityPublished

CVE-2026-35200: parse-server · Interpretation Conflict

Affects parse-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.1 Low : upgrade to 9.7.1-alpha.4 or 8.6.73 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
2.1Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.7.1-alpha.4, 8.6.73
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade parse-server to 9.7.1-alpha.4 or 8.6.73; parse-community/parse-server to 8.6.73.

Affected software

ProductAffectedFixed in
parse-communityparse-serverAffected
  • >=9.0.0 <9.7.1-alpha.4
Fixed in
  • 9.7.1-alpha.4
parse-communityparse-serverAffected
  • <8.6.73
Fixed in
  • 8.6.73
GitHubparse-community/parse-serverpkg:github/parse-community/parse-serverOther threatsAffected
  • <8.6.73
Fixed in
  • 8.6.73

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in parse-server versions 8.6.73 and 9.7.1-alpha.4. Users should upgrade to these or later versions to resolve the issue. Since this is a cloud service, the vendor manages remediation for hosted services; users should verify with the vendor if using a managed parse-server instance. No additional mitigation steps are indicated by the vendor advisory.

Description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 8.6.73 and 9.7.1, 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. This vulnerability is fixed in 8.6.73 and 9.7.1.

References

Community reviews

Loading reviews…