CVE-2026-32140: Dataease remote code execution (CVSS 8.8)

Description

Dataease is an open source data visualization analysis tool. Prior to 2.10.20, By controlling the IniFile parameter, an attacker can force the JDBC driver to load an attacker-controlled configuration file. This configuration file can inject dangerous JDBC properties, leading to remote code execution. The Redshift JDBC driver execution flow reaches a method named getJdbcIniFile. The getJdbcIniFile method implements an aggressive automatic configuration file discovery mechanism. If not explicitly restricted, it searches for a file named rsjdbc.ini. In a JDBC URL context, users can explicitly specify the configuration file via URL parameters, which allows arbitrary files on the server to be loaded as JDBC configuration files. Within the Redshift JDBC driver properties, the parameter IniFile is explicitly supported and used to load an external configuration file. This vulnerability is fixed in 2.10.20.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Dataease< 2.10.20

Remediation

Fixed in

Dataease≥ 2.10.20

Patch & vendor advisories

https://github.com/dataease/dataease/security/advisories/GHSA-jc9q-3jfw-mch4

References

https://github.com/dataease/dataease/security/advisories/GHSA-jc9q-3jfw-mch4ExploitVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-32140 being actively exploited?

CVE-2026-32140 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.91%.

How severe is CVE-2026-32140?

CVE-2026-32140 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.91% probability of exploitation.

Which products are affected by CVE-2026-32140?

Affected products include Dataease.

How do I fix CVE-2026-32140?

Upgrade affected software to a fixed version, for example Dataease 2.10.20 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-32140 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo