CVE-2025-36041 is a medium severity (CVSS 4.7) certificate validation flaw in IBM MQ Operator, where Native HA CRR could be configured with a private key and chain other than the intended one. Update to the fixed operator and MQ Advanced images named in IBM's bulletin.
What's affected
The record lists these IBM MQ Operator releases: LTS 2.0.0 through 2.0.29, 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 and 3.5.1 through 3.5.3, and SC2 3.2.0 through 3.2.12. Supplied MQ Advanced container images are also listed.
IBM's bulletin names these remedies: MQ Operator v3.6.0 CD with the 9.4.3.0-r1 image, MQ Operator v3.2.13 SC2 with the 9.4.0.11-r3 image, and the MQ Container 9.4.3.0-r1 release. The bulletin covers several other issues in the same release. Its note on this CVE says it is applicable only to Operator v3.6.0 CD and the 9.4.3.0-r1 image, which differs from the wider version list in the record, so read the bulletin for your exact release line.
IBM's own vector is local access, high complexity and high privileges, which explains the medium score. The record does not mark it exploited in the wild, and it is not on the CISA Known Exploited Vulnerabilities list.
How to check if you're exposed
- List your installed operator version. On OpenShift or Kubernetes, check the operator subscription or the cluster service version for the MQ operator.
- List the MQ container image tags used by your queue managers, for example with kubectl describe on the pods.
- Compare both with the lists in the bulletin.
- Find whether you use Native HA with cross region replication, called CRR. If not, review the bulletin to see whether the issue applies to you.
- Review which certificates and keys are configured for the CRR replication links.
What to do now
- Read IBM's bulletin and identify which of the fixed releases fits your channel.
- Upgrade the operator and the MQ container images in a test cluster first.
- Check that each Native HA CRR configuration references the intended private key and certificate chain.
- Limit who can edit queue manager resources and secrets, since the weakness rests on configuration.
- Run an image scan on your MQ images. You can start with the free in-browser scan at gold.safeguard.sh/scan and the Gold directory.
Why it matters
The class is CWE-295, improper certificate validation. Mutual trust between replicated queue managers depends on each side presenting the right identity. If the wrong key and chain can be used, one party may trust something it should not.
The score is modest because exploitation needs high privileges and local access. Still, message queues carry business data between systems, so identity mistakes in replication links deserve attention in a regular patch cycle.
Quick check
Which fixed releases does IBM name?
MQ Operator v3.6.0 CD with image 9.4.3.0-r1, MQ Operator v3.2.13 SC2 with image 9.4.0.11-r3, and MQ Container 9.4.3.0-r1.
Why is the severity only medium?
IBM's vector needs local access and high privileges, and attack complexity is high.
Sources
Last reviewed: 18 October 2026.
