DataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase template saves call TemplateManageService#save, StaticResourceServer#saveFilesToServe, and the /de2api/templateManage/save endpoint with attacker-controlled staticResource names and Base64 content, allowing path traversal and arbitrary file writes because only / was used when extracting the file name. This issue is fixed in version 2.10.23.
CVE-2026-45419
HIGHPre-NVD 8.58.5
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.5 under the CNA's CVSS (NVD's own analysis pending). 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).
Triggered by: NVD CVSS baseline
Sources: cna:github_m
8.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 8.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.5
- EG Score
- 8.5(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available
Arbitrary File Write Vulnerability · Advisory · dataease/dataease · GitHub
Affected: v2.10.23.
https://github.com/dataease/dataease/security/advisories/GHSA-83fh-fgh3-g9f9github_release Patch Available
v2.10.23
Patch available: dataease/dataease v2.10.23
https://github.com/dataease/dataease/releases/tag/v2.10.23github_commit
commit d34f413ef047 (dataease/dataease)
Fix landed in dataease/dataease commit d34f413ef047 — awaiting tagged release
https://github.com/dataease/dataease/commit/d34f413ef047bd275909d67310d200cbc8ae31baWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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-07-15 19:45 UTCEG score recompute
- 2026-07-15 19:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-45419?
CVE-2026-45419 is a high vulnerability published on July 15, 2026. DataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase template saves call TemplateManageService#save, StaticResourceServer#saveFilesToServe, and the /de2api/templateManage/save endpoint with attacker-controlled staticResource names and Base64 content, allowing…
When was CVE-2026-45419 disclosed?
CVE-2026-45419 was first published in the National Vulnerability Database on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-45419?
CVE-2026-45419 has a CVSS v3 base score of 8.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-45419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45419, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-45419
Is Your Infrastructure Affected by CVE-2026-45419?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.