Loading vulnerability…
CVE-2025-36041 affects 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 in Native HA CRR configurations. According to the provided description, the product could be configured with a private key and certificate chain other than the intended key. This indicates an authorization or trust-binding failure in certificate/key handling, where an unintended credential set may be accepted for a security-sensitive configuration. Successful exploitation could undermine the integrity of the intended trust relationship and expose protected communications or privileged operations to misuse.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept exploit for CVE-2025-36041, a vulnerability in IBM MQ that allows bypassing SSL certificate validation. The main exploit is implemented in 'exploit.c', a C program that uses the IBM MQ client libraries to connect to a target IBM MQ server. By specifying a path to a fake SSL KeyRepository, a queue name, and a queue manager name via command-line arguments, the exploit attempts to establish a connection to the MQ server (defaulting to 127.0.0.1:1414 and SYSTEM.DEF.SVRCONN channel), bypass SSL certificate checks, open the specified queue, and send a test message ('Hello MQ'). Successful execution demonstrates the ability to connect and interact with the MQ server without valid SSL credentials, confirming the vulnerability. The repository also includes a detailed README with build and usage instructions, and an 'end.txt' file containing background information on IBM MQ and the vulnerability. No hardcoded credentials or external network endpoints are present beyond the default local MQ connection parameters. The exploit is a functional PoC and not weaponized, requiring the attacker to provide the necessary parameters and have access to the target MQ network.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.