dbcve.org
DataeaseApplication

CVE-2025-58046

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 2.10.13 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 platform. In versions up to and including 2.10.12, the Impala data source is vulnerable to remote code execution due to insufficient filtering in the getJdbc method of the io.dataease.datasource.type.Impala class. Attackers can construct malicious JDBC connection strings that exploit JNDI injection and trigger RMI deserialization, ultimately enabling remote command execution. The vulnerability can be exploited by editing the data source and providing a crafted JDBC connection string that references a remote configuration file, leading to RMI-based deserialization attacks. This issue has been patched in version 2.10.13. It is recommended to upgrade to the latest version. No known workarounds exist for affected versions.

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 up to 2.10.12 contain an RCE vulnerability in the Impala data source connector. The getJdbc method in io.dataease.datasource.type.Impala lacks proper filtering of JDBC connection strings, allowing JNDI injection where attackers embed malicious RMI references in the connection string to trigger deserialization and achieve remote command execution.

MitigationUpgrade to Dataease version 2.10.13 or later. No workarounds exist for affected versions; immediate patching is required given the critical CVSS score.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DataeaseApplication
Affected:< 2.10.13

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installed Dataease version
    Check the Dataease version by logging into the application and navigating to 'About' or 'System Settings', or inspect the version.properties/version.json file in the Dataease installation directory.
    Affected if The installed version is any release prior to 2.10.13 (versions 2.10.12 and below are affected).
  2. Verify if Impala data source is configured
    In the Dataease web interface, navigate to 'Data Sources' or 'Data Source Management' and examine the list of configured data sources. Look for any data source with type 'Impala' or 'Impala JDBC'.
    Affected if An Impala data source is present in the configuration, meaning the vulnerable getJdbc method could process malicious connection strings.
  3. Inspect JDBC connection string handling
    Decompile or inspect the Impala.java class file, specifically the getJdbc method. Look for whether the JDBC URL/connection string is passed directly to the driver without sanitization or allowlist validation.
    Affected if The getJdbc method accepts and uses the JDBC connection string directly without filtering out patterns like 'ldap://', 'rmi://', or other JNDI lookup protocols.

If the Dataease version is below 2.10.13 AND the Impala connector class exists (regardless of whether an Impala data source is actively configured), the environment is vulnerable to CVE-2025-58046.

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
Upgrade available Upgrade to 2.10.13 or later
Fixed in 2.10.13
Vendor patch github.com →
Interim mitigation

Upgrade to Dataease version 2.10.13 or later. No workarounds exist for affected versions; immediate patching is required given the critical CVSS score.

Recommended fix High confidence

2.10.13

  1. Upgrade Dataease to version 2.10.13 or later as the vulnerability has been patched in that release
  2. After upgrading, verify the Impala data source connector now properly filters JDBC connection strings
  3. Review existing Impala data source configurations to ensure no malicious connection strings were introduced prior to the upgrade
  4. If unable to upgrade immediately, disable the Impala data source type until the upgrade can be performed

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

Fix this in Dataease Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58046 — 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-2025-58046 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