CVE-2026-45417

HIGHPre-NVD 8.78.7
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.7 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.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: CVSS: 8.7Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

DataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase datasource connection status checks concatenate configuration.getSchema() into getTablesSql and execute the resulting SQL with executeQuery in io.dataease.datasource.provider.CalciteProvider#checkStatus, allowing SQL injection against DB2, SQL Server, PostgreSQL, and other affected datasources. This issue is fixed in version 2.10.23.

CVSS v3
8.7
EG Score
8.7(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

SQL injection vulnerability · Advisory · dataease/dataease · GitHub

Affected: v2.10.23.

https://github.com/dataease/dataease/security/advisories/GHSA-rg6c-r9mv-39fr
github_release Patch Available

v2.10.23

Patch available: dataease/dataease v2.10.23

https://github.com/dataease/dataease/releases/tag/v2.10.23
github_commit

commit f1c7204da178 (dataease/dataease)

Fix landed in dataease/dataease commit f1c7204da178 — awaiting tagged release

https://github.com/dataease/dataease/commit/f1c7204da1787ef812ee23cd3d51a1824126c1fb

Weakness 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.

  1. 2026-07-15 19:45 UTCEG score recompute
  2. 2026-07-15 19:44 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-45417?
CVE-2026-45417 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 datasource connection status checks concatenate configuration.getSchema() into getTablesSql and execute the resulting SQL with executeQuery in io.dataease.datasource.provider.CalciteProvider#checkStatus,…
When was CVE-2026-45417 disclosed?
CVE-2026-45417 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-45417?
CVE-2026-45417 has a CVSS v3 base score of 8.7 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-45417?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45417, 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-45417

Explore →

Is Your Infrastructure Affected by CVE-2026-45417?

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