Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.4 and 8.6.30, an attacker can upload a file with a file extension or content type that is not blocked by the default configuration of the Parse Server fileUpload.fileExtensions option. The file can contain malicious code, for example JavaScript in an SVG or XHTML file. When the file is accessed via its URL, the browser renders the file and executes the malicious code in the context of the Parse Server domain. This is a stored Cross-Site Scripting (XSS) vulnerability that can be exploited to steal session tokens, redirect users, or perform actions on behalf of other users. Affected file extensions and content types include .svgz, .xht, .xml, .xsl, .xslt, and content types application/xhtml+xml and application/xslt+xml for extensionless uploads. Uploading of .html, .htm, .shtml, .xhtml, and .svg files was already blocked. This vulnerability is fixed in 9.6.0-alpha.4 and 8.6.30.
CVE-2026-31868
This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(low)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity61% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
March 11, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/parse-community/parse-server/releases/tag/8.6.30
- security-advisories@githubhttps://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.4
- security-advisories@githubhttps://github.com/parse-community/parse-server/security/advisories/GHSA-v5hf-f4c3-m5rv
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| parse-server | — | 9.6.0-alpha.4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:41 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-31868?
When was CVE-2026-31868 disclosed?
Is CVE-2026-31868 actively exploited?
What is the CVSS score of CVE-2026-31868?
How do I remediate CVE-2026-31868?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31868
Is Your Infrastructure Affected by CVE-2026-31868?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.