dbcve.org
MqApplication · Ibm

CVE-2025-36100

MEDIUM · 5.5 CVSS v3.1 Published 2025-09-07
Fix available
A fix is available. Upgrade to 9.1.0.31 / 9.2.0.37 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MqApplication
Affected:>= 9.1.0.0, < 9.1.0.31>= 9.2.0.0, < 9.2.0.37>= 9.3.0.0, < 9.3.0.31>= 9.3.0.0, <= 9.3.5.1>= 9.4.0.0, < 9.4.0.15>= 9.4.0.0, < 9.4.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.1.0.31 / 9.2.0.37 / 9.3.0.31 or later
Fixed in 9.1.0.319.2.0.379.3.0.31
Vendor patch www.ibm.com →
Recommended fix High confidence

9.1.0.31 / 9.2.0.37 / 9.3.0.31 (or later respective versions)

  1. 1. Identify the current IBM MQ version by running 'dspmqver' or checking the installation directory
  2. 2. Download IBM MQ 9.1.0.31 or later for 9.1.x installations, 9.2.0.37 or later for 9.2.x installations, or 9.3.0.31 or later for 9.3.x installations from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
  3. 3. Review IBM MQ upgrade documentation for your specific platform before proceeding
  4. 4. Stop all IBM MQ queue managers and listeners on the affected system
  5. 5. Apply the upgrade following IBM's standard installation/upgrade procedure for your platform
  6. 6. Restart the queue managers and verify IBM MQ is running correctly
  7. 7. Enable trace temporarily and verify that passwords are no longer being written to client configuration files (the fix prevents this behavior)
Caveat Review IBM MQ upgrade notes for your specific version jump - some platform-specific considerations may apply; always test upgrade in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36100 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36100 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data