IBM MQ Operator
IBM MQ improper certificate validation
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2.0.0 LTS, <= 2.0.29 LTS
- 3.0.0, 3.0.1, 3.1.0, 3.1.3, 3.4.0, 3.5.0, 3.5.1, 3.5.3 CD
- >= 3.2.0 SC2, <= 3.2.10 SC2
Mitigation
Issues mentioned by this security bulletin are addressed in - IBM MQ Operator v3.6.0 CD release that included IBM supplied MQ Advanced 9.4.3.0-r1 container image. IBM MQ Operator v3.2.13 SC2 release that included IBM supplied MQ Advanced 9.4.0.11-r3 container image. IBM MQ Container 9.4.3.0-r1 release. Note: CVE-2025-36041 is applicable only for IBM MQ Operator v3.6.0 CD and IBM supplied MQ Advanced 9.4.3.0-r1 container image. IBM strongly recommends applying the latest container images.
References
- Vendor advisory ibm.com/support/pages/node/7236608
Timeline
Days relative to CVE publicationFirst public PoC 4.4 days after publication; not in CISA KEV. First PoC: byteReaper77/CVE-2025-36041 (created 19 Jun 2025, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| byteReaper77/CVE-2025-36041 | 19 Jun 2025 +4.4 d | 2 | PoC
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.