CVE-2025-11159

Hitachi Vantara Pentaho Data Integration And Analytics vulnerability

9.1 CRITICALEPSS 0.34%

Published13 May 2026

Description

Hitachi Vantara Pentaho Data Integration & Analytics of all versions contain a JDBC driver for H2 databases which is vulnerable to external script execution when a new connection is created by a data source administrator.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredHigh

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

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

Affected products

Hitachi Vantara Pentaho Data Integration And Analytics< 10.2.0.7

Remediation

Fixed in

Hitachi Vantara Pentaho Data Integration And Analytics≥ 10.2.0.7

Patch & vendor advisories

https://support.pentaho.com/hc/en-us/articles/39954640408077--Resolved-Hitachi-Vantara-Pentaho-Data-Integration-Analytics-Dependency-on-Vulnerable-Third-Party-Component-Versions-before-10-2-0-7-and-11-0-0-0-Impacted-CVE-2025-11159

References

https://support.pentaho.com/hc/en-us/articles/39954640408077--Resolved-Hitachi-Vantara-Pentaho-Data-Integration-Analytics-Dependency-on-Vulnerable-Third-Party-Component-Versions-before-10-2-0-7-and-11-0-0-0-Impacted-CVE-2025-11159Vendor Advisory

Frequently asked

Is CVE-2025-11159 being actively exploited?

CVE-2025-11159 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.34%.

How severe is CVE-2025-11159?

CVE-2025-11159 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.34% probability of exploitation.

Which products are affected by CVE-2025-11159?

Affected products include Hitachi Vantara Pentaho Data Integration And Analytics.

How do I fix CVE-2025-11159?

Upgrade affected software to a fixed version, for example Hitachi Vantara Pentaho Data Integration And Analytics 10.2.0.7 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-11159 against the real software inventory on every managed device, every day. 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

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.