CVE-2026-32939 DataEase is Vulnerable to H2 JDBC RCE Bypass
Attackers can execute arbitrary code by exploiting locale-based case conversion discrepancies to bypass JDBC URL validation filters.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-32939?
CVE-2026-32939 is a high-severity code injection vulnerability in Dataease Dataease, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-178
Which versions are affected by CVE-2026-32939?
It affects 1 product.
Products include Dataease Dataease.
How do I fix CVE-2026-32939?
No fix has been published for CVE-2026-32939 yet. Limit exposure of the affected software until one is available.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
Is CVE-2026-32939 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32939 exists.
Other vulnerabilities in Dataease Dataease
- CVE-2024-57707 Code injection in n/a
- CVE-2024-46997 DataEase's H2 datasource has a remote command execution risk
- CVE-2023-33963 DataEase data source has deserialization vulnerability
- CVE-2023-28437 SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed
- CVE-2022-39312 Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability
Sources
Also known as GHSA-pj7p-3m49-52qq.