Security readout for executives and security teams
Plain-English summary
DataEase versions before 2.10.23 have a critical remote code execution flaw in Redshift datasource handling. An authenticated attacker may be able to make a normal database connection load hostile configuration from the Java temporary directory, leading to code execution. Upgrade priority is high for any DataEase deployment using or allowing Redshift datasource connections.
Executive priority
Treat this as urgent for exposed or multi-user DataEase environments. The issue can lead to full compromise of the DataEase server, but current sources do not show confirmed exploitation in the wild.
Technical view
The flaw is in DataEase Redshift datasource connections. The Redshift JDBC driver can load attacker-controlled rsjdbc.ini from java.io.tmpdir and instantiate a configured socketFactory, enabling a reflection-based RCE chain during connection handling. Sources identify io.dataease.datasource.type.Redshift and Redshift driver methods as the affected path. Fixed in 2.10.23.
Likely exposure
Exposure appears limited to DataEase versions before 2.10.23, especially deployments where authenticated users can configure or trigger Redshift datasource connections. The bundle does not identify other datasource types or products as affected.
Exploitation context
The CVSS vector indicates network reachability, low privileges, no user interaction, high impact, high attack complexity, and required attack conditions. KEV is false, and the provided sources do not cite active exploitation or public weaponization.
Researcher notes
Evidence is strongest for the Redshift datasource path and versions before 2.10.23. The advisory describes a configuration-loading and object-instantiation chain, but validation should avoid exploit reproduction and focus on version, permissions, feature exposure, and vendor-confirmed fixes.
Mitigation direction
- Upgrade DataEase to version 2.10.23 or later.
- Review vendor advisory and release notes for any additional hardening guidance.
- Restrict who can create, edit, or test Redshift datasource connections.
- Audit DataEase temporary directories for unexpected JDBC configuration files.
- Monitor DataEase for unusual datasource connection attempts or failures.
Validation and detection
- Inventory all DataEase deployments and record their versions.
- Confirm no production instance remains below 2.10.23.
- Identify whether Redshift datasource support is enabled or used.
- Review datasource permission assignments for low-privileged accounts.
- Check logs for recent Redshift datasource connection activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-45534 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/dataease/dataease/security/advisories/GHSA-cv4c-8rpv-2x97CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/dataease/dataease/commit/3e58149f1e014b1a7ae2c12134b37ae438f676acCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/dataease/dataease/releases/tag/v2.10.23CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.