DataEase is an open source data visualization and analysis tool. Versions prior to 2.10.23 have a path traversal vulnerability. The root cause is that on Windows, the FILE_SEPARATOR is \, while the server only filters the / character during string truncation. The vulnerability has been fixed in v2.10.23. No known workarounds are available.
CVE-2026-45532
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 70(Attend)EG Risk 70/100SSVC: Attend
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 computedSeverity87% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 18, 2026
Advisory Details (2)
Auto-updated Aug 18, 2026v2.10.23
Patch available: dataease/dataease v2.10.23
https://github.com/dataease/dataease/releases/tag/v2.10.23Path Traversal Vulnerability · Advisory · dataease/dataease · GitHub
Affected: v2.10.23.
https://github.com/dataease/dataease/security/advisories/GHSA-2mqc-w4hm-f3p9Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 24× 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-30 01:22 UTCEPSS rescore
- 2026-08-29 04:41 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 20:02 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 18:14 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 15:47 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 02:56 UTCEG score recompute
- 2026-08-24 14:05 UTCEG score recompute
- 2026-08-23 12:20 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 10:37 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 08:54 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 18:20 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 16:37 UTCEG score recompute
- 2026-08-18 16:00 UTCEG score recompute
- 2026-08-18 13:20 UTCEG score recompute
- 2026-08-18 13:06 UTCEG score recompute
- 2026-08-18 13:06 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-45532?
When was CVE-2026-45532 disclosed?
Is CVE-2026-45532 actively exploited?
What is the CVSS score of CVE-2026-45532?
How do I remediate CVE-2026-45532?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-45532
Is Your Infrastructure Affected by CVE-2026-45532?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.