dbcve.org
Integration BusApplication · Ibm

CVE-2025-36014

MEDIUM · 6.7 CVSS v3.1 Published 2025-07-07
Fix available
A fix is available. Upgrade to after 10.1.0.5 or later.
See remediation →
69/100
Remediation priority · Elevated
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
IBM Integration Bus for z/OS 10.1.0.0 through 10.1.0.5 is vulnerable to code injection by a privileged user with access to the IIB install directory.

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

IBM Integration Bus for z/OS versions 10.1.0.0 through 10.1.0.5 allows a privileged user with access to the IIB install directory to inject malicious code, likely through modification of executable files, scripts, or configuration files within the installation path.

MitigationRestrict filesystem access to the IIB install directory to only essential privileged personnel, and apply any available IBM patches or upgrade to a fixed version beyond 10.1.0.5.

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
Integration BusApplication
Affected:>= 10.1.0.0, <= 10.1.0.5

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

CVSS:3.1/AV:L/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. Confirm IBM Integration Bus for z/OS is installed
    Locate the IIB installation directory on the z/OS system. Common locations include /usr/lients/iib or installation-specific paths. Use 'ls -la' to verify the directory exists and contains IIB components.
    Affected if The product IBM Integration Bus for z/OS is present in the environment
  2. Determine the installed version
    Check the version of IIB by examining version files in the installation directory (such as version.info) or by running the IIB command 'mqsireportversion'. Compare the version number against the affected range.
    Affected if The installed version falls within 10.1.0.0 through 10.1.0.5 inclusive
  3. Review filesystem permissions on the IIB installation directory
    Examine access controls on the IIB install directory using z/OS commands like 'ls -ld' or security product commands (RACF, ACF2, or equivalent) to list which users or groups have write or modify permissions.
    Affected if Users other than essential privileged personnel have write or modify access to the IIB install directory

The environment is affected if IBM Integration Bus for z/OS version 10.1.0.0 through 10.1.0.5 is installed and untrusted or non-essential users have filesystem write access to the installation directory.

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 a release after 10.1.0.5
Interim mitigation

Restrict filesystem access to the IIB install directory to only essential privileged personnel, and apply any available IBM patches or upgrade to a fixed version beyond 10.1.0.5.

Recommended fix Moderate confidence

IBM Integration Bus 10.1.0.6 or later, or migrate to latest supported IBM App Connect Enterprise (successor product)

  1. 1. Identify the current IBM Integration Bus version in use by checking the installation directory or using IIB command-line tools.
  2. 2. Review IBM's official security bulletin for CVE-2025-36014 at ibm.com/support to confirm the exact fixed version and any specific patch requirements.
  3. 3. Schedule a maintenance window for the upgrade process.
  4. 4. Back up the current IIB installation, including configuration files, integration flows, and any custom resources.
  5. 5. Download and install IBM Integration Bus version 10.1.0.6 or later (or the latest available 10.1.x version) from IBM Fix Central or IBM Passport Advantage.
  6. 6. Restore configuration and redeploy integration applications after upgrade.
  7. 7. Verify that the IIB node starts successfully and all deployed flows function correctly.
  8. 8. Validate that the code injection vulnerability is resolved by confirming the fixed version is running.
Caveat Review IBM migration guides for potential compatibility changes between 10.1.0.x versions; test thoroughly in non-production environment before production deployment

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

Fix this in Integration Bus Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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