CVE-2026-32728

HIGHNVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.6 under NVD CVSS v3. EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-12973 (ENISA EUVD) · GHSA-42ph-pf9q-cr72 (GitHub Security Advisories)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.15 and 8.6.41, an attacker who is allowed to upload files can bypass the file extension filter by appending a MIME parameter (e.g. ;charset=utf-8) to the Content-Type header. This causes the extension validation to fail matching against the blocklist, allowing active content to be stored and served under the application's domain. In addition, certain XML-based file extensions that can render scripts in web browsers are not included in the default blocklist. This can lead to stored XSS attacks, compromising session tokens, user credentials, or other sensitive data accessible via the browser's local storage. The fix in versions 9.6.0-alpha.15 and 8.6.41 strips MIME parameters from the Content-Type header before validating the file extension against the blocklist. The default blocklist has also been extended to include additional XML-based extensions (xsd, rng, rdf, rdf+xml, owl, mathml, mathml+xml) that can render active content in web browsers. Note that the fileUpload.fileExtensions option is intended to be configured as an allowlist of file extensions that are valid for a specific application, not as a denylist. The default denylist is provided only as a basic default that covers most common problematic extensions. It is not intended to be an exhaustive list of all potentially dangerous extensions. Developers should not rely on the default value, as new extensions that can render active content in browsers might emerge in the future. As a workaround, configure the fileUpload.fileExtensions option to use an allowlist of only the file extensions that your application needs, rather than relying on the default blocklist.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 18, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Aug 2, 2026
Patch available. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)

Stored XSS filter bypass via Content-Type MIME parameter and missing XML extension blocklist entries · Advisory · parse-community/parse-server · GitHub

https://github.com/parse-community/parse-server/security/advisories/GHSA-42ph-pf9q-cr72
GitHub pull request Patch Available

fix: Stored XSS filter bypass via Content-Type MIME parameter and missing XML extension blocklist entries (GHSA-42ph-pf9q-cr72)

Patch available: parse-community/parse-server 8.6.81 (PR #10192 merged 2026-03-13)

https://github.com/parse-community/parse-server/pull/10192
GitHub pull request Patch Available

fix: Stored XSS filter bypass via Content-Type MIME parameter and missing XML extension blocklist entries (GHSA-42ph-pf9q-cr72)

Patch available: parse-community/parse-server 9.9.1-alpha.6 (PR #10191 merged 2026-03-13)

https://github.com/parse-community/parse-server/pull/10191
GitHub commit Patch Available

commit c7599c577a02 (parse-community/parse-server)

Patch available: parse-community/parse-server 8.6.81 (contains commit c7599c577a02)

https://github.com/parse-community/parse-server/commit/c7599c577a02b97eb5e76d4e20517b0283ae73c8
GitHub commit Patch Available

commit 4f53ab3cad55 (parse-community/parse-server)

Patch available: parse-community/parse-server 9.9.1-alpha.6 (contains commit 4f53ab3cad55)

https://github.com/parse-community/parse-server/commit/4f53ab3cad5502a51a509d53f999e00ff7217b8d

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmparse-server @ 9.6.0-alpha.15 (fixes >= 9.0.0, < 9.6.0-alpha.15)—ghsa
npmparse-server @ 8.6.41 (fixes < 8.6.41)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
parse-server—
  • 9.0.0 up to 9.6.0-alpha.15: fixed in 9.6.0-alpha.15
  • every version up to 8.6.41: fixed in 8.6.41
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 109 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 13 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-11-01 07:54 UTCGHSA enrichmentGHSA-42ph-pf9q-cr72 · GitHub severity HIGH
  3. 2026-11-01 07:54 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-10-30 16:38 UTCEG score recompute
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-25 14:35 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-10-24 04:14 UTCEG score recompute
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-18 03:47 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-10-17 15:49 UTCEG score recompute
  24. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Show 71 more
  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  4. 2026-10-12 16:14 UTCEG score recompute
  5. 2026-10-11 19:56 UTCEG score recompute
  6. 2026-10-11 17:09 UTCEG score recompute
  7. 2026-10-11 14:36 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-10-11 09:44 UTCOSV refresh
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-09-21 22:15 UTCOSV refresh
  25. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  26. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  27. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  28. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  29. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  30. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  31. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  32. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  33. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  34. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  35. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  36. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  37. 2026-09-02 18:08 UTCOSV refresh
  38. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  39. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  40. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  41. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  42. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  43. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  44. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  45. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  46. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  47. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  48. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  49. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  50. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  51. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  52. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  53. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  54. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  55. 2026-08-16 11:14 UTCEG score recompute
  56. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  57. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  58. 2026-08-14 07:22 UTCEG score recompute
  59. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  60. 2026-08-12 22:09 UTCEG score recompute
  61. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  62. 2026-08-11 21:30 UTCEG score recompute
  63. 2026-08-11 04:34 UTCEG score recompute
  64. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  65. 2026-08-09 19:16 UTCEG score recompute
  66. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  67. 2026-08-09 06:57 UTCEG score recompute
  68. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  69. 2026-08-07 17:29 UTCEG score recompute
  70. 2026-08-06 19:28 UTCEG score recompute
  71. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-32728?
CVE-2026-32728 is a high-severity vulnerability; its CVE record was published on March 18, 2026. 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.15 and 8.6.41, an attacker who is allowed to upload files can bypass the file extension filter by appending a MIME parameter (e.g. ;charset=utf-8) to the Content-Type header.…
When was the CVE record for CVE-2026-32728 published?
The CVE record for CVE-2026-32728 was published on March 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-32728 actively exploited?
CVE-2026-32728 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32728?
CVE-2026-32728 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-32728?
A fix for CVE-2026-32728 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32728

Explore →

Is Your Infrastructure Affected by CVE-2026-32728?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs