CVE-2026-32939: DataEase is Vulnerable to H2 JDBC RCE Bypass
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 (trTR), 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-32939?
CVE-2026-32939 has been classified as a critical vulnerability due to its potential for remote code execution.
How do I fix CVE-2026-32939?
To fix CVE-2026-32939, upgrade DataEase to version 2.10.20 or later, which contains the necessary patches.
What versions of DataEase are affected by CVE-2026-32939?
CVE-2026-32939 affects all DataEase versions up to and including 2.10.19.
What type of vulnerability is CVE-2026-32939?
CVE-2026-32939 is a remote code execution vulnerability due to improper handling of JDBC URL validation.
Is DataEase still safe to use if I am on a version higher than 2.10.19?
Yes, DataEase is safe to use if you are on version 2.10.20 or newer, as these versions have addressed the vulnerability.