CVE-2026-53751

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%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.24, the H2 database JDBC URL validation logic can be bypassed with special Unicode characters whose case-conversion behavior differs between DataEase validation and H2 parsing, allowing attackers to smuggle dangerous parameters such as init in malicious H2 JDBC connection strings and achieve arbitrary code execution. This issue is fixed in version 2.10.24.

CVSS v3
8.7
EG Score
8.7(medium)
EPSS
29.7%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 8, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

H2 JDBC URL Filter Bypass Leads to Remote Code Execution (RCE) · Advisory · dataease/dataease · GitHub

Affected: v2.10.24.

https://github.com/dataease/dataease/security/advisories/GHSA-xjhm-r8p8-c2cg
github_release Patch Available

v2.10.24

Patch available: dataease/dataease v2.10.24

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

commit 2204258118ea (dataease/dataease)

Fix landed in dataease/dataease commit 2204258118ea — awaiting tagged release

https://github.com/dataease/dataease/commit/2204258118eac6160a6636ca20dbedb0d3f95747

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 30× 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 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 13:57 UTCEG score recompute
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 00:43 UTCEG score recompute
  7. 2026-07-14 11:28 UTCEG score recompute
  8. 2026-07-13 22:31 UTCEPSS rescore
  9. 2026-07-13 22:16 UTCEG score recompute
  10. 2026-07-13 09:04 UTCEG score recompute
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-12 19:52 UTCEG score recompute
  14. 2026-07-12 06:40 UTCEG score recompute
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 17:28 UTCEG score recompute
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 04:16 UTCEG score recompute
  20. 2026-07-10 15:04 UTCEG score recompute
  21. 2026-07-10 01:50 UTCEG score recompute
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 12:39 UTCEG score recompute
  25. 2026-07-08 23:27 UTCEG score recompute
Show 5 more
  1. 2026-07-08 15:16 UTCEPSS rescore
  2. 2026-07-08 15:16 UTCEPSS rescore
  3. 2026-07-08 10:15 UTCEG score recompute
  4. 2026-07-07 21:03 UTCEG score recompute
  5. 2026-07-07 21:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53751?
CVE-2026-53751 is a high vulnerability published on July 7, 2026. DataEase is an open source data visualization and analysis tool. Prior to 2.10.24, the H2 database JDBC URL validation logic can be bypassed with special Unicode characters whose case-conversion behavior differs between DataEase validation and H2 parsing, allowing attackers to smuggle dangerous…
When was CVE-2026-53751 disclosed?
CVE-2026-53751 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53751 actively exploited?
CVE-2026-53751 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53751?
CVE-2026-53751 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-53751?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53751, 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-53751

Explore →

Is Your Infrastructure Affected by CVE-2026-53751?

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