Skip to main content

IBM MQ CVE-2025-36128

HIGH
Missing Release of Resource after Effective Lifetime (CWE-772)
2025-10-16 psirt@us.ibm.com
7.5
CVSS 3.1 · Vendor: us
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed MQ listener over network
  2. Delivery
    Open many slow/partial connections
  3. Exploit
    Starve per-read timeout enforcement
  4. Execution
    Exhaust connection resources
  5. Impact
    Deny service to legitimate clients

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Resource cleanup on lifecycle end
Exploitation Conditions

Exploitation requires network reachability to an IBM MQ queue manager TCP listener (default channel port, commonly 1414) on an affected version (9.1/9.2/9.3/9.4 LTS or 9.3/9.4 CD). The root cause is improper enforcement of the timeout on individual read operations, so the attacker exploits slow/incomplete reads (slowloris-type) to hold connections open. No authentication, credentials, or user interaction are needed (PR:N/UI:N). The practical limiting factor is exposure: impact is confined to availability, and risk is bounded by whether the listener is reachable from untrusted networks versus isolated behind firewalls/VPN or protected by connection rate-limiting and timeout controls; internal-only queue managers face substantially lower real-world exposure.

Impact

This is a moderate-priority availability issue rather than a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) confirms a network-reachable, low-complexity, unauthenticated, no-interaction attack with impact limited solely to availability (C:N/I:N) - consistent with the slowloris-style resource-exhaustion denial of service described. The signals are internally consistent: a slowloris attack does fit AV:N/AC:L/PR:N. However, the quantitative exploitation signals temper the raw score: EPSS is only 0.54% (44th percentile), the CVE is NOT on the CISA KEV list, and no public exploit code is referenced, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The 7.5 is driven entirely by ease of reach and high availability impact, not by confidentiality/integrity loss or observed in-the-wild activity. Net: treat as a standard patch-cycle item for internet- or partner-facing MQ listeners, escalating only where MQ availability is business-critical and the queue manager listener is exposed to untrusted networks. No key signals are contradictory; the main limitation is that slowloris techniques are generic and well understood, so weaponization is plausible even without published PoC.

Exploit ScenarioDerived

A remote, unauthenticated attacker opens many TCP connections to an exposed IBM MQ queue manager listener and sends partial/slow read-triggering traffic, holding each connection open because the per-read timeout is not properly enforced. Accumulated half-open or stalled connections exhaust connection/resource limits, preventing legitimate clients from connecting and effectively taking the messaging service offline. No public exploit is referenced, but slowloris tooling is generic and readily adaptable.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 09, 2026

Denial of service in IBM MQ 9.1, 9.2, 9.3 and 9.4 LTS and 9.3/9.4 Continuous Delivery lets remote unauthenticated attackers hold queue manager connections open with slow or incomplete read operations, draining connection and thread resources until legitimate messaging clients can no longer connect. The root cause is improper enforcement of the timeout on individual read operations (CWE-772, resource not released after its effective lifetime), and exploitation requires only network reachability to an IBM MQ TCP listener such as the default channel port 1414 - no credentials or user interaction are needed (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5). Impact is confined to availability: EPSS is 0.54% (~44th percentile), no public exploit code has been identified at time of analysis, and there is no confirmed active exploitation (CISA KEV), making this a moderate-priority availability issue whose real-world risk is bounded by whether the listener is exposed to untrusted networks.

RemediationAI

Confirm your affected level against the IBM advisory at https://www.ibm.com/support/pages/node/7244480 and apply the vendor-supplied fix pack or maintenance level IBM lists for your MQ version - exact patched version numbers are not included in the source data for this CVE, so take the specific level from that advisory rather than assuming one; the available patch status is 'Patch available per vendor advisory' rather than a version independently confirmed here. Where patching must be staged, the highest-value compensating control is exposure reduction: stop publishing the channel listener (default 1414) to untrusted networks, restrict it with host/network firewall allowlists, VPN or private interconnect so only known client subnets can reach it - the trade-off is that any legitimate remote or partner client on a disallowed path breaks immediately. On the queue manager, use CHLAUTH rules and TLS with SSLPEER to require client certificates so only authenticated, expected clients can open channels, and set/reduce client idle timeouts (for example channel HBINT and TCP keepalive/KAINT settings) so stalled connections are reaped faster; be aware that aggressive idle timeouts and keepalive values can terminate legitimately slow or long-idle applications. At the network edge, apply per-source connection rate limiting or a load balancer/proxy that caps concurrent connections per client IP, understanding that NAT-shared sources may be throttled collectively. Note that lowering MAXCHANNELS or MAXHANDS is a blunt control that can also block legitimate clients during normal peaks, so prefer patching plus scoped reachability restrictions.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

IBM MQ is enterprise messaging middleware; a queue manager accepts client and channel connections through TCP listeners, with server-connection (SVRCONN) channels typically served on port 1414 unless reconfigured. The vulnerability class is CWE-772, 'Missing Release of Resource after Effective Lifetime': the queue manager fails to properly enforce the timeout applied to individual read operations, so a partially sent or deliberately stalled message keeps the associated connection and its processing resources allocated well past the intended lifetime. This is the classic slowloris pattern applied to a messaging broker - an attacker opens many connections and advances each one slowly enough to stay under the idle threshold, so a relatively small number of sockets can exhaust the connection/handler pool and starve legitimate clients. The assessed vector is unauthenticated and remote (PR:N/UI:N) with availability-only impact (C:N/I:N/A:H), consistent with resource-exhaustion rather than data exposure or message tampering; the practical limiting factor is network reachability to the listener, since internal-only queue managers behind firewalls or VPN gateways face substantially lower exposure.

Know when Mq gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (us) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 7.5 HIGH

Remote unauthenticated slowloris over the network needs no privileges or interaction (AV:N/AC:L/PR:N/UI:N); impact is availability-only resource exhaustion (C:N/I:N/A:H), scope unchanged.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (us).

CVSS VectorVendor: us

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

DescriptionCVE.org

IBM MQ 9.1, 9.2, 9.3, 9.4 LTS and 9.3, 9.4 CD is vulnerable to a denial of service, caused by improper enforcement of the timeout on individual read operations. By conducting slowloris-type attacks, a remote attacker could exploit this vulnerability to cause a denial of service.

Executive ViewAI

Why It Matters

IBM MQ 9.1, 9.2, 9.3, and 9.4 LTS and Continuous Delivery deployments are vulnerable to a remote denial-of-service attack that can exhaust connection and thread resources, preventing legitimate messaging clients from connecting. This unauthenticated flaw requires only network reachability to an MQ TCP listener such as the default port 1414, so any internet-facing queue manager represents an immediate availability risk to business-critical messaging flows. With no vendor patch available, leadership must prioritize reducing exposure and monitoring for anomalous connection behavior while awaiting an official fix.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis; restrict network access to IBM MQ listeners (e.g., block port 1414 from untrusted networks), enforce connection rate limits and idle timeouts at the network layer, disable unnecessary channels, monitor for connection exhaustion, and segment MQ infrastructure behind firewalls or VPNs.

Threat Intelligence Overview

EPSS Score
0.5%
Top 56% exploitable
Prevalence
High
widely deployed enterprise messaging middleware across banking and large enterprises
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Medium

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

Affected Products (CPE)CVE.org

cpe:2.3:a:ibm:mq:9.1.0.0:*:*:*:lts:*:*:*
cpe:2.3:a:ibm:mq:9.2.0.0:*:*:*:lts:*:*:*
cpe:2.3:a:ibm:mq:9.3.0:*:*:*:continuous_delivery:*:*:*
cpe:2.3:a:ibm:mq:9.3.0.0:*:*:*:lts:*:*:*
cpe:2.3:a:ibm:mq:9.4.0:*:*:*:continuous_delivery:*:*:*
cpe:2.3:a:ibm:mq:9.4.0.0:*:*:*:lts:*:*:*

More in Mq

View all
CVE-2026-12351 CRITICAL
9.8 Sep 15

Remote code execution in IBM MQ is possible when the optional IVT (Installation Verification Test) application is deploy

CVE-2026-10027 CRITICAL
9.8 Sep 18

Malformed compressed data delivered over an IBM MQ channel that has compression enabled can trigger an out-of-bounds hea

CVE-2022-22489 CRITICAL
9.1 Aug 19

IBM MQ 8.0, (9.0, 9.1, 9.2 LTS), and (9.1 and 9.2 CD) are vulnerable to an XML External Entity Injection (XXE) attack wh

CVE-2026-11375 HIGH
8.8 Sep 18

IBM MQ queue managers that process XA (X/Open distributed) transactions are vulnerable to a memory-corruption buffer ove

CVE-2026-11378 HIGH
8.8 Sep 18

Integer overflow (CWE-190) in IBM MQ distribution list processing lets an authenticated user with PUT authority to a dis

CVE-2026-12728 HIGH
8.8 Sep 15

Authenticated remote code execution in IBM MQ lets an attacker who holds valid MQ credentials - or who can reach a chann

CVE-2026-10575 HIGH
8.8 Sep 18

Heap-based buffer overflow in IBM MQ allows an authenticated, low-privilege attacker who can reach a queue manager to ca

CVE-2026-11725 HIGH
8.8 Sep 18

An integer overflow in IBM MQ's MQINQ (inquire object attributes) request processing lets an authenticated remote user c

CVE-2026-10853 HIGH
8.8 Sep 18

IBM MQ queue managers running affected releases can be crashed - and, per IBM, potentially have arbitrary code executed

CVE-2024-31912 HIGH
8.8 Jun 28

IBM MQ 9.3 LTS and 9.3 CD could allow an authenticated user to escalate their privileges under certain configurations du

CVE-2026-11729 HIGH
8.5 Sep 15

Unsafe Java object deserialization in IBM MQ (9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS / 9.3.0.0

CVE-2026-11728 HIGH
8.1 Sep 15

A heap buffer overflow in the IBM MQ client (CWE-787) can be triggered when the client processes crafted messages delive

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy