dbcve.org
App Connect EnterpriseApplication · Ibm

CVE-2025-36361

HIGH · 8.8 CVSS v3.1 Published 2025-10-24
Fix available
A fix is available. Upgrade to after 13.0.4.2 or later.
See remediation →
94/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
IBM App Connect Enterprise 13.0.1.0 through 13.0.4.2, and 12.0.1.0 through 12.0.12.17 could allow an authenticated user to perform unauthorized actions on customer defined resources due to missing authorization.

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

IBM App Connect Enterprise versions 12.x and 13.x contains a missing authorization check that allows authenticated users to perform unauthorized actions on customer-defined resources. This is a broken access control vulnerability where the application fails to validate user permissions before allowing operations on resources.

MitigationApply the vendor-supplied security patch for IBM App Connect Enterprise to a version beyond 13.0.4.2 (for v13) or 12.0.12.17 (for v12), or upgrade to the latest supported release.

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
App Connect EnterpriseApplication
Affected:>= 12.0.1.0, <= 12.0.12.17>= 13.0.1.0, <= 13.0.4.2

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

CVSS:3.1/AV:N/AC:L/PR:L/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 IBM App Connect Enterprise installation
    Locate the installation directory and run 'mqsireportversion' command from the installation bin directory, or check the installed packages via system package manager
    Affected if IBM App Connect Enterprise is installed on the system
  2. Determine installed version number
    Examine the output of mqsireportversion or check version files in the installation directory to obtain the exact version (for example, 12.0.x.x or 13.0.x.x)
    Affected if Version cannot be determined or command fails
  3. Compare version against affected ranges
    Check if the installed version falls within 12.0.1.0 through 12.0.12.17, or within 13.0.1.0 through 13.0.4.2
    Affected if Installed version is within either of these ranges
  4. Verify if REST or admin APIs are accessible
    Check configuration files (broker.xml, policy files) or running services to determine if REST APIs or administrative interfaces are exposed and require authentication
    Affected if The system exposes REST or admin APIs to authenticated users without additional authorization controls

You are affected if IBM App Connect Enterprise version 12.0.1.0-12.0.12.17 or 13.0.1.0-13.0.4.2 is installed and the system exposes accessible APIs or administrative interfaces 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 a release after 13.0.4.2
Interim mitigation

Apply the vendor-supplied security patch for IBM App Connect Enterprise to a version beyond 13.0.4.2 (for v13) or 12.0.12.17 (for v12), or upgrade to the latest supported release.

Recommended fix Moderate confidence

Upgrade to IBM App Connect Enterprise 12.0.13.0+ (for 12.x users) or 13.0.5.0+ (for 13.x users)

  1. 1. Identify the current IBM App Connect Enterprise version in use by checking the installation or consulting IBM documentation.
  2. 2. For version 12.x deployments: Plan upgrade to version 12.0.13.0 or later (the first version after 12.0.12.17 that includes the security fix).
  3. 3. For version 13.x deployments: Plan upgrade to version 13.0.5.0 or later (the first version after 13.0.4.2 that includes the security fix).
  4. 4. Review IBM App Connect Enterprise upgrade documentation for your deployment type (container, on-premise, etc.).
  5. 5. Test the upgrade in a non-production environment before deploying to production.
  6. 6. Schedule maintenance window and apply the upgrade following IBM's standard upgrade procedures.
  7. 7. Verify the upgrade was successful and confirm the new version is running.
Caveat Review IBM release notes for your target version; upgrades between major versions may require compatibility testing of integrations and configurations

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

Fix this in App Connect Enterprise Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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