CVE-2026-32939: DataEase is Vulnerable to H2 JDBC RCE Bypass

Vulnerability summary

CVE-2026-32939 is a high (CVSS 8.1) Improper Handling of Case Sensitivity vulnerability in dataease. EPSS estimates a 0.46% chance of exploitation in the next 30 days, higher than 40.3% of scored vulnerabilities. 1 public exploit is recorded.

Timeline

1. 20-03-2026
   PublishedVulnerability first disclosed.
2. 20-03-2026
   Last modifiedVulnerability information updated.

Description

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.

• CWE-178Improper Handling of Case SensitivityThe product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.