Sensitive-data disclosure via unintended CRR certificate chain
Published Jun 15, 2025 · Updated Aug 24, 2025
Improper certificate validation in affected IBM MQ Operator releases allows local users to disclose data or perform unauthorized actions. Native HA CRR certificate handling accepts a configured private key and certificate chain without confirming that they are the intended credentials. Exploitation requires local high-privilege access and high-complexity conditions; successful substitution exposes sensitive information or enables unauthorized actions.
Summary
What happened
Improper certificate validation in affected IBM MQ Operator releases allows local users to disclose data or perform unauthorized actions. Native HA CRR certificate handling accepts a configured private key and certificate chain without confirming that they are the intended credentials. Exploitation requires local high-privilege access and high-complexity conditions; successful substitution exposes sensitive information or enables unauthorized actions.
The record
- CVE
- CVE-2025-36041
- Published
- Jun 15, 2025
- Updated
- Aug 24, 2025
- Vendor
- IBM
- Product
- IBM MQ Operator
- Classifications
- CWE-295
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 15, 2025CVE publishedPublication date reported by the CVE source.
- Aug 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 LTS <=2.0.29 LTS
- Affected versionversion=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
- Affected versionversion=3.2.0 SC2 <=3.2.10 SC2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo