dbcve.org
Vantara Pentaho Data Integration And AnalyticsApplication · Hitachi

CVE-2025-11158

CRITICAL · 9.1 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.2.0.6 or later.
See remediation →
97/100
Remediation priority · Urgent
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 versions before 10.2.0.6, including 9.3.x and 8.3.x, do not restrict Groovy scripts in new PRPT reports published by users, allowing insertion of arbitrary scripts and leading to a RCE.

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

Hitachi Vantara Pentaho Data Integration & Analytics fails to restrict Groovy script execution in PRPT report definitions, allowing authenticated users to inject and execute arbitrary code on the server, resulting in remote code execution.

MitigationUpgrade to Pentaho version 10.2.0.6 or later which enforces Groovy script restrictions, or apply vendor-supplied patches to affected versions.

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

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 the installed Pentaho Data Integration & Analytics version
    Check the product version displayed in the Pentaho user interface, or locate the version file in the Pentaho installation directory (typically found in version.properties or RELEASE_NOTES files within the installation root)
    Affected if The installed version is lower than 10.2.0.6 (e.g., 10.1, 9.x, 8.x series)
  2. Confirm PRPT report functionality is accessible
    Verify that the Pentaho Reporting module is enabled and users can access the report designer or upload PRPT report definition files through the Pentaho user console or API
    Affected if PRPT report creation, editing, or execution capabilities are available to authenticated users
  3. Determine if Groovy script execution is permitted in reports
    Examine the Pentaho configuration files (such as pentaho.objects.spring.xml or report-engine-config.xml) for settings controlling Groovy script execution within PRPT report definitions, or test by creating a sample PRPT with a Groovy expression
    Affected if Groovy scripting is not explicitly disabled or sandboxed in the Pentaho configuration, allowing arbitrary code execution through PRPT report definitions

The environment is affected if Pentaho Data Integration & Analytics version is below 10.2.0.6 AND the PRPT report module with Groovy script execution capability is accessible to authenticated users.

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.6 or later
Fixed in 10.2.0.6
Interim mitigation

Upgrade to Pentaho version 10.2.0.6 or later which enforces Groovy script restrictions, or apply vendor-supplied patches to affected versions.

Recommended fix High confidence

10.2.0.6

  1. Identify the current Pentaho Data Integration & Analytics version in use
  2. Download Pentaho Data Integration & Analytics version 10.2.0.6 or later from the official Hitachi Vantara support portal
  3. Plan and execute the upgrade following Hitachi Vantara's official upgrade documentation
  4. After upgrading, verify that the Groovy script execution restriction is now enforced in PRPT reports
  5. Test that the new PRPT report functionality works correctly without allowing arbitrary Groovy script execution

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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