Vulnerability in Parseplatform (CVE-2026-35200)
Summary
Vulnerability in Parseplatform (CVE-2026-35200). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.6.73 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-35200 has been found in Parseplatform.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade Parseplatform to 8.6.73 or later.
If unsure, ask your IT team or search "Parseplatform CVE-2026-35200" on the vendor's site.
CVE-2026-35200 (Parseplatform) — CWE-436 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Patched: 8.6.73 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-436) exists in Parseplatform.
Check the vendor advisory for the affected versions of Parseplatform.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 8.6.73.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Parseplatform' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Parseplatform' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Parseplatformを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Parseplatform to 8.6.73ステージング環境で 8.6.73 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- patch github.com
- patch github.com
- web nvd.nist.gov