Read the docs
TI-2026-25387 Aliases CVE-2026-32939

DataEase is Vulnerable to H2 JDBC RCE Bypass

Priority HIGH 69CWE-178Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

DataEase is an open source data visualization analysis tool. Versions 2.10.19 and below have inconsistent Locale handling between the JDBC URL validation logic and the H2 JDBC engine's internal parsing. DataEase uses String.toUpperCase() without specifying an explicit Locale, causing its security checks to rely on the JVM's default runtime locale, while H2 JDBC always normalizes URLs using Locale.ENGLISH. In Turkish locale environments (tr_TR), Java converts the lowercase letter i to İ (dotted capital I) instead of the standard I, so a malicious parameter like iNIT becomes İNIT in DataEase's filter (bypassing its blacklist) while H2 still correctly interprets it as INIT. This discrepancy allows attackers to smuggle dangerous JDBC parameters past DataEase's security validation, and the issue has been confirmed as exploitable in real DataEase deployment scenarios running under affected regional settings. The issue has been fixed in version 2.10.20.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00475 41st percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed dataease (dataease): 2.10.20

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
dataeasedataeasebefore 2.10.202.10.20Patch availableCNA
  • dataease Vendordataease Affected before 2.10.20 Fixed in 2.10.20 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:*before 2.10.20Vulnerabledataease
  • cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:* Versions before 2.10.20 Vulnerable ·dataease

Remediation

  • Fix · CNA dataease (dataease) Fixed in 2.10.20

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-32939
  2. 2026-10-18 EPSS moved to the 50th–90th percentile
  3. 2026-10-25 EPSS moved to the below the 50th percentile

References

Exploit 1

Patch 1

Other 1

  • TI-2024-38037 An issue in DataEase v1 allows an attacker to execute arbitrary code via the user account and password components. CVSS 3.1CRITICAL 9.8
  • TI-2023-12981 SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed CVSS 3.1CRITICAL 9.8
  • TI-2022-18688 Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability CVSS 3.1CRITICAL 9.8
  • TI-2026-24677 Dataease: Redshift JDBC RCE Bypass CVSS 4.0CRITICAL 9.3
  • TI-2026-24674 DataEase SQL Injection Vulnerability CVSS 4.0CRITICAL 9.3
  • TI-2024-37398 DataEase has an unauthorized vulnerability CVSS 4.0CRITICAL 9.3
See all 71 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences