DataEase SQL Injection in Datasource Metadata Identifiers
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- SQL injection
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-89.
Summary
DataEase, an open source data visualization and analysis tool, has SQL injection in datasource metadata identifiers (CWE-89). Authenticated users with datasource access can supply crafted schema names, connection usernames, table names, or database names to getSchema, validate, save, and update. CalciteProvider places these identifiers into queries run through a plain JDBC Statement, so an attacker can alter the SQL and run it against the backend with the application's datasource credentials. Exploitation can compromise confidentiality, integrity, and availability of the connected database without victim action.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Description from the CNA
DataEase is an open source data visualization and analysis tool. Authenticated users with datasource access can supply crafted schema names, connection usernames, table names, or database names to datasource metadata operations, including getSchema, validate, save, and update flows. CalciteProvider inserts these identifiers into metadata queries that are executed through a plain JDBC Statement, allowing the generated SQL to be altered and run against the configured backend with application-held datasource credentials. The issue can compromise the confidentiality, integrity, and availability of the connected database without requiring a victim action.
Why it matters now
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
Remediation
Upgrade DataEase to version 2.10.26 or later. The affected range is versions before 2.10.26, and no fix is listed in the advisory data for this range, so confirm the fixed release with the vendor before relying on it.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
- Fix · CNA dataease (dataease) Fixed in 2.10.26
Timeline
- 2026-10-15 Threatist record created from CVE-2026-104141
- 2026-10-15 CISA SSVC decision points changed
- 2026-10-15 Priority changed: MEDIUM → HIGH
References
More dataease vulnerabilities
- 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
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences