dbcve.org
Vantara Pentaho Data Integration And AnalyticsApplication · Hitachi

CVE-2026-2253

HIGH · 7.7 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 10.2.0.7 / 11.0.0.0 or later.
See remediation →
83/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 versions before 10.2.0.7 and 11.0.0.0, including 9.3.x and 8.3.x, does not prevent certain XML parsers from resolving external entities.

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

This is an XML External Entity (XXE) injection vulnerability in Hitachi Vantara Pentaho Data Integration & Analytics. The software does not prevent certain XML parsers from resolving external entities, allowing attackers to inject malicious XXE payloads into XML input. This can lead to disclosure of internal files, denial of service, or server-side request forgery.

MitigationUpgrade to Pentaho Data Integration & Analytics version 10.2.0.7 or 11.0.0.0 or later. Alternatively, disable external entity resolution in XML parser configurations.

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> 10.2.0.8, < 11.0.0.0= 8.3= 9.3

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

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

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 version
    Locate the version file or check the product About dialog. Common locations include version.properties in the installation directory or the version info displayed in the Pentaho Data Integration splash screen on startup.
    Affected if The installed version is 8.3, 9.3, or falls in the range < 10.2.0.7 OR > 10.2.0.8 AND < 11.0.0.0 (for example, 10.1, 10.2.0.0 through 10.2.0.8)
  2. Determine if XML processing features are in use
    Review your Pentaho repository or job/transformation files for usage of steps such as 'Get Data from XML', 'XML Input Stream', 'XML Join', or any job entries that parse XML documents.
    Affected if XML parsing steps or job entries that process user-submitted or external XML files are configured and active in your environment
  3. Inspect XML parser configuration for external entity settings
    Examine the Pentaho configuration files (such as pentaho.xml or similar XML parser configuration files in the installation directory) for parser settings related to external entity resolution, disallowing-doctype-decl, or similar XXE-prevention flags.
    Affected if The XML parser configurations allow external entity resolution (feature is not explicitly disabled) or no XXE protection settings are present

Your environment is affected if the installed Pentaho version matches the affected ranges AND XML processing of untrusted documents is performed with default parser settings.

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 / 11.0.0.0 or later
Fixed in 10.2.0.711.0.0.0
Interim mitigation

Upgrade to Pentaho Data Integration & Analytics version 10.2.0.7 or 11.0.0.0 or later. Alternatively, disable external entity resolution in XML parser configurations.

Recommended fix High confidence

Upgrade to Pentaho Data Integration & Analytics 10.2.0.7 or 11.0.0.0 (or later)

  1. 1. Identify the current Pentaho Data Integration & Analytics version in use
  2. 2. Download the fixed version (10.2.0.7 or 11.0.0.0 or later) from support.pentaho.com
  3. 3. Review the upgrade guide and release notes for the target version
  4. 4. Perform a backup of existing configurations, repositories, and databases
  5. 5. Stop all Pentaho services
  6. 6. Install the new version following the standard upgrade procedure
  7. 7. Restore configurations and repositories from backup
  8. 8. Restart Pentaho services

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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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