CVE-2025-36041: IBM MQ Operator · Improper Certificate Validation
Affects IBM MQ OperatorSource CVE Database V5
Not known to be exploited · CVSS 4.7 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM MQ Operator | Affected
| Fixed in– |
AI-suggested
European organizations should immediately review and audit their IBM MQ Operator configurations, especially focusing on the Native HA CRR setup to ensure that private keys and certificate chains are correctly configured and match intended values. Access to systems running MQ Operator should be restricted to trusted administrators with minimal necessary privileges to reduce the risk of malicious configuration changes. Implement strict role-based access controls (RBAC) and monitor for unusual configuration changes or certificate usage. Organizations should stay alert for IBM security advisories and apply patches or updates as soon as they become available. Additionally, consider implementing certificate pinning or validation checks external to the MQ Operator to detect anomalies. Regularly audit logs related to MQ Operator operations and certificate management to detect potential misuse. Network segmentation can further limit the exposure of MQ Operator components to only trusted network zones. Finally, conduct internal penetration testing focused on privilege escalation and certificate validation weaknesses to identify and remediate gaps before attackers can exploit them.
Description
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 through 3.5.3, and MQ Operator SC2 3.2.0 through 3.2.12 Native HA CRR could be configured with a private key and chain other than the intended key which could disclose sensitive information or allow the attacker to perform unauthorized actions.