dbcve.org
Vantara Pentaho Data Integration And AnalyticsApplication · Hitachi

CVE-2025-11159

HIGH · 7.2 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 10.2.0.7 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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
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.

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 · moderate confidence

Hitachi Vantara Pentaho Data Integration & Analytics ships with a JDBC driver for H2 databases that contains a vulnerability allowing external script execution. When a data source administrator creates a new H2 database connection, the driver can be leveraged to execute arbitrary scripts on the host system, potentially leading to code execution or data exfiltration.

MitigationDisable or remove the H2 JDBC driver from Pentaho installations if not required, or apply vendor-provided configuration changes to restrict script execution capabilities in H2 connections. Network segmentation can limit exposure from this authenticated vulnerability.

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
Vantara Pentaho Data Integration And AnalyticsApplication
Affected:< 10.2.0.7

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

CVSS:3.1/AV:N/AC:L/PR:H/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 Pentaho version
    Locate the version file in the Pentaho installation directory (typically version.txt or in the system information), or check the 'About' dialog in the Pentaho user console. Compare the version number against 10.2.0.7.
    Affected if The installed version is lower than 10.2.0.7 and the H2 JDBC driver is present in the installation.
  2. Locate H2 JDBC driver in Pentaho
    Search for H2 database driver files in the Pentaho lib directory (commonly at [pentaho-installation]/lib/ or [pentaho-installation]/data-integration/lib/). Look for files named h2*.jar.
    Affected if The H2 JDBC driver JAR file exists in the Pentaho libraries directory.
  3. Identify configured H2 database connections
    Inspect Pentaho datasource configuration files for H2 connection definitions. Check XML files in the Pentaho solutions directory (typically under /system/datasources/ or /publishing/), .xmi files, and repository metadata files. Look for connection strings containing 'jdbc:h2:' or driver class 'org.h2.Driver'.
    Affected if One or more H2 database connections are defined in Pentaho configuration files.
  4. Check H2 connection script execution settings
    Review the H2 connection configuration files for INIT, INIT_CONTEXT, or RUNSCRIPT parameters in the JDBC connection string. These parameters allow script execution on connection establishment.
    Affected if H2 connections are configured with INIT, INIT_CONTEXT, or RUNSCRIPT parameters that enable script execution.

You are affected if Pentaho version is below 10.2.0.7 AND the H2 JDBC driver is present AND an H2 database connection has been configured in Pentaho.

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 10.2.0.7 or later
Fixed in 10.2.0.7
Interim mitigation

Disable or remove the H2 JDBC driver from Pentaho installations if not required, or apply vendor-provided configuration changes to restrict script execution capabilities in H2 connections. Network segmentation can limit exposure from this authenticated vulnerability.

Recommended fix Moderate confidence

10.2.0.7 or later

  1. Back up your current Pentaho Data Integration & Analytics installation and configuration
  2. Download Pentaho Data Integration & Analytics version 10.2.0.7 or later from the official Hitachi Vantara support portal (support.pentaho.com)
  3. Stop all Pentaho services and server instances
  4. Install the upgraded version following the standard Pentaho upgrade procedure
  5. Restart Pentaho services
  6. Verify that the H2 JDBC driver has been updated to the fixed version
  7. Test that data source connections to H2 databases work correctly with the new driver

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

Fix this in Vantara Pentaho Data Integration And Analytics Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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