dbcve.org
Mq OperatorApplication · Ibm

CVE-2025-27365

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-01
Fix available
A fix is available. Upgrade to after 3.2.10 or later.
See remediation →
71/100
Remediation priority · Elevated
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 MQ Operator LTS 2.0.0 through 2.0.29, MQ Operator CD 3.0.0, 3.0.1, 3.1.0 through 3.1.3, 3.3.0, 3.4.0, 3.4.1, 3.5.0, 3.5.1, and MQ Operator SC2 3.2.0 through 3.2.10  Client connecting to a MQ Queue Manager can cause a SIGSEGV in the AMQRMPPA channel process terminating it.

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

A denial of service vulnerability in IBM MQ Operator allows a client connecting to a MQ Queue Manager to trigger a SIGSEGV (segmentation fault) in the AMQRMPPA channel process, causing it to terminate unexpectedly. This affects multiple LTS, CD, and SC2 versions of the MQ Operator.

MitigationUpgrade IBM MQ Operator to a version beyond the affected releases (consult IBM fix list). Implement monitoring for AMQRMPPA process crashes and consider queuing high-availability configurations to minimize service disruption during operator updates.

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
Mq OperatorApplication
Affected:>= 2.0.0, <= 2.0.29>= 2.2.0, <= 2.2.2>= 2.3.0, <= 2.3.3>= 2.4.0, <= 2.4.8>= 3.1.0, <= 3.1.3>= 3.2.0, <= 3.2.10= 3.0.0= 3.0.1= 3.3.0= 3.4.0= 3.4.1= 3.5.0
Supplied Mq Advanced Container ImagesApplication
Affected:= 9.2.0.1= 9.2.0.2= 9.2.0.4= 9.2.0.5= 9.2.0.6= 9.2.3.0= 9.2.4.0= 9.2.5.0= 9.3.0.0= 9.3.0.1= 9.3.0.3= 9.3.0.4

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 MQ Operator version in cluster
    Run 'kubectl get deployment -n <mq-namespace> -l app.kubernetes.io/name=mq-operator -o jsonpath="{.items[*].spec.template.spec.containers[0].image}"' or check the operator CSV version with 'kubectl get csv -n <mq-namespace>'
    Affected if The operator version falls within: 2.0.0-2.0.29, 2.2.0-2.2.2, 2.3.0-2.3.3, 2.4.0-2.4.8, 3.1.0-3.1.3, 3.2.0-3.2.10, or is exactly 3.0.0, 3.0.1, 3.3.0, 3.4.0, 3.4.1, or 3.5.0
  2. Identify MQ Queue Manager container image version
    Run 'kubectl get qmgr -n <mq-namespace> -o jsonpath="{.items[*].spec.template.spec.containers[0].image}"' to retrieve the MQ container images in use
    Affected if The container image version is exactly: 9.2.0.1, 9.2.0.2, 9.2.0.4, 9.2.0.5, 9.2.0.6, 9.2.3.0, 9.2.4.0, 9.2.5.0, 9.3.0.0, 9.3.0.1, 9.3.0.3, or 9.3.0.4
  3. Check for AMQRMPPA process crashes in logs
    Search pod logs for SIGSEGV or AMQRMPPA termination events: 'kubectl logs -n <mq-namespace> <qmgr-pod> --previous | grep -i "SIGSEGV\|AMQRMPPA\|segmentation"'
    Affected if Logs show unexpected AMQRMPPA process termination or segmentation faults related to client channel connections
  4. Verify client channel listener is configured
    Check Queue Manager listener configuration with 'kubectl get qmgr <qm-name> -n <mq-namespace> -o jsonpath={.spec.listeners}' or inspect the listener pod for port 1414 (or configured MQ port) being exposed for client connections
    Affected if A listener is configured to accept client connections (TCP/1414 by default), enabling the vulnerable AMQRMPPA channel process path

The environment is affected if the IBM MQ Operator version OR the MQ container image version matches the affected ranges AND client connections to the Queue Manager are enabled, as this triggers the vulnerable AMQRMPPA channel process.

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.

From vendor data
Upgrade available Upgrade to a release after 3.2.10
Interim mitigation

Upgrade IBM MQ Operator to a version beyond the affected releases (consult IBM fix list). Implement monitoring for AMQRMPPA process crashes and consider queuing high-availability configurations to minimize service disruption during operator updates.

Fix this in Mq Operator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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