dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-45534

CRITICAL · 9.0 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
DataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase Redshift datasource connections can load attacker-controlled rsjdbc.ini configuration from System.getProperty("java.io.tmpdir"), setting socketFactory=org.springframework.context.support.FileSystemXmlApplicationContext so com.amazon.redshift.Driver#connect, com.amazon.redshift.Driver#getJdbcIniFile, and com.amazon.redshift.util.ObjectFactory#instantiate execute a reflection-based remote code execution chain during a normal JDBC connection through io.dataease.datasource.type.Redshift. This issue is fixed in version 2.10.23.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

DataEase versions prior to 2.10.23 have a path traversal vulnerability in the Redshift datasource connector. The connector loads the rsjdbc.ini configuration file from java.io.tmpdir without validation, allowing attackers to place a malicious ini file that specifies a Spring FileSystemXmlApplicationContext as socketFactory. During normal JDBC connection through io.dataease.datasource.type.Redshift, the com.amazon.redshift.Driver#connect and related methods instantiate this attacker-controlled class via reflection, achieving remote code execution.

MitigationUpgrade DataEase to version 2.10.23 or later. Additionally, restrict write access to the temporary directory and monitor for unauthorized rsjdbc.ini files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify DataEase installation and version
    Locate the DataEase installation directory and find its version information (typically in a version file, about page, or pom.xml within the application). Compare your installed version against the fixed version 2.10.23.
    Affected if DataEase version is lower than 2.10.23 and the Redshift connector is in use.
  2. Confirm Redshift datasource connector is configured
    Review DataEase datasource configurations to determine if a Redshift (Amazon Redshift) datasource has been created or is active in the environment.
    Affected if A Redshift datasource is configured or was recently used in DataEase.
  3. Inspect java.io.tmpdir for rsjdbc.ini files
    Examine the Java temporary directory (java.io.tmpdir, often /tmp or a Windows temp folder) for any rsjdbc.ini files. List all files matching this name.
    Affected if An rsjdbc.ini file exists in the temp directory and contains attacker-controlled socketFactory or other malicious configuration.
  4. Verify temp directory write permissions
    Check file system permissions on the java.io.tmpdir directory to determine if unprivileged users or processes can write files to this location.
    Affected if The temp directory is world-writable or writable by untrusted users, allowing placement of a malicious rsjdbc.ini file.

If DataEase version is below 2.10.23, the Redshift connector is active, and the temp directory either contains an rsjdbc.ini file with malicious socketFactory settings or is writable by attackers, the environment is vulnerable to CVE-2026-45534.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade DataEase to version 2.10.23 or later. Additionally, restrict write access to the temporary directory and monitor for unauthorized rsjdbc.ini files.

Recommended fix High confidence

DataEase version 2.10.23

  1. 1. Back up your current DataEase installation and database
  2. 2. Download DataEase version 2.10.23 from the official GitHub releases page (github.com/dataease/dataease)
  3. 3. Stop the DataEase service
  4. 4. Install version 2.10.23 following the standard upgrade procedure for your deployment method
  5. 5. Start the DataEase service
  6. 6. Verify the Redshift datasource connector works correctly in version 2.10.23
  7. 7. Confirm the vulnerability is remediated by testing a Redshift connection
Caveat Review release notes for 2.10.23 to check for any breaking changes; standard upgrade precautions apply (backup before upgrading)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45534 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45534 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data