CVE-2026-45534
Critical RCE in DataEase via malicious rsjdbc.ini loaded from java.io.tmpdir
Is CVE-2026-45534 being exploited?
Not confirmed. CVE-2026-45534 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.64% probability of exploitation in the next 30 days.
How severe is CVE-2026-45534?
CVE-2026-45534 is rated Critical with a CVSS score of 9.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-45534?
Yes. A fix has been recorded for CVE-2026-45534. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-45534 affect?
CVE-2026-45534 affects DataEase <2.10.23, DataEase Redshift datasource, Amazon Redshift JDBC (rsjdbc.ini), Java hosts using io.dataease.datasource.type.Redshift. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-45534?
Upgrade to DataEase 2.10.23 and remove/restrict untrusted rsjdbc.ini in java.io.tmpdir
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution on hosts running DataEase during Redshift JDBC connects by loading attacker-controlled rsjdbc.ini.
Immediate action required
- affected< 2.10.23
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.