CVE-2026-1713: IBM MQ · Authentication Bypass by Primary Weakness
Affects IBM MQSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMMQ | Affected
| Fixed in– |
Mavencom.ibm.mq/mqpkg:maven/com.ibm.mq/mqOther threats | Affected
| Fixed in– |
CPE configurations (11)
cpe:2.3:a:ibm:mq:9.1.0.0:*:*:*:*:*:*:*cpe:2.3:a:ibm:mq:9.1.0.33:*:*:*:*:*:*:*cpe:2.3:a:ibm:mq:9.2.0.0:*:*:*:*:*:*:*cpe:2.3:a:ibm:mq:9.2.0.40:*:*:*:*:*:*:*cpe:2.3:a:ibm:mq:9.3.0.0:*:*:*:*:*:*:*cpe:2.3:a:ibm:mq:9.3.0.36:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate the risk posed by CVE-2026-1713, organizations should take the following specific actions: 1) Monitor IBM's official security advisories and apply patches or updates immediately once they become available for the affected IBM MQ versions. 2) Implement strict network segmentation to isolate IBM MQ servers from untrusted networks and limit access to only authorized systems and users. 3) Enforce strong access controls and authentication mechanisms at the network level, such as VPNs, IP whitelisting, and firewall rules restricting inbound connections to IBM MQ ports. 4) Enable and review detailed logging and monitoring of IBM MQ access and message traffic to detect unusual or unauthorized activities promptly. 5) Consider deploying additional authentication layers or gateway proxies that can enforce authentication before traffic reaches IBM MQ servers. 6) Conduct regular security assessments and penetration testing focused on IBM MQ environments to identify and remediate potential weaknesses. 7) Educate system administrators and security teams about the vulnerability and the importance of rapid response. These measures will help reduce exposure until official patches are deployed and ensure early detection of potential exploitation attempts.
Description
IBM MQ 9.1.0.0 through 9.1.0.33 LTS, 9.2.0.0 through 9.2.0.40 LTS, 9.3.0.0 through 9.3.0.36 LTS, 9.30.0 through 9.3.5.1 CD, 9.4.0.0 through 9.4.0.17 LTS, and 9.4.0.0 through 9.4.4.1 CD