dbcve.org
Mq ApplianceApplication · Ibm

CVE-2025-0975

HIGH · 8.8 CVSS v3.1 Published 2025-02-28
Fix available
A fix is available. Upgrade to after 9.4.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 9.3 LTS, 9.3 CD, 9.4 LTS, and 9.4 CD console could allow an authenticated user to execute code due to improper neutralization of escape characters.

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 · high confidence

IBM MQ console versions 9.3 LTS, 9.3 CD, 9.4 LTS, and 9.4 CD contain a command injection vulnerability where improper neutralization of escape characters allows an authenticated attacker to execute arbitrary code on the underlying system through the console interface.

MitigationApply IBM's official patches for this vulnerability to all affected IBM MQ installations. Restrict console access to only necessary authenticated users until patches are applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Mq ApplianceApplication
Affected:>= 9.3.0, <= 9.4.2>= 9.3.0.0, <= 9.3.0.27>= 9.4.0.0, <= 9.4.0.10

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine IBM MQ console version
    Run the dspmqver command on the system or check the MQ installation directory for version information. Compare the installed version against the affected ranges: 9.3.0.0 through 9.3.0.27, 9.4.0.0 through 9.4.0.10, and 9.3.0 through 9.4.2.
    Affected if The installed version falls within any of these ranges: 9.3.0.0-9.3.0.27, 9.4.0.0-9.4.0.10, or 9.3.0-9.4.2
  2. Verify console web interface is enabled
    Check whether the IBM MQ console service is running and accessible. This is typically configured via the mqweb server or console configuration. Inspect the console listening ports and endpoints in your environment.
    Affected if The console web interface is enabled and network-accessible
  3. Review console user accounts and privileges
    List all user accounts authorized to access the IBM MQ console. Examine the console user configuration to identify which authenticated users have access and their assigned privilege levels.
    Affected if Console authentication is enabled and any user account can log in to the console
  4. Inspect console audit logs for suspicious activity
    Review IBM MQ console audit and trace logs for any anomalous commands, unexpected code execution, or escape character manipulation attempts that may indicate exploitation of this vulnerability.
    Affected if Console logs contain unexpected commands or evidence of injection attempts

The environment is affected if the installed IBM MQ console version falls within the vulnerable ranges AND the console interface is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 a release after 9.4.2
Interim mitigation

Apply IBM's official patches for this vulnerability to all affected IBM MQ installations. Restrict console access to only necessary authenticated users until patches are applied.

Recommended fix Moderate confidence

IBM MQ 9.3 LTS: 9.3.0.28+; IBM MQ 9.4 LTS: 9.4.0.11+; IBM MQ 9.4 CD: 9.4.3+

  1. 1. Identify your current IBM MQ Appliance version using 'mqversion' command or the web console.
  2. 2. For IBM MQ 9.3 LTS (9.3.0.0 through 9.3.0.27): Upgrade to 9.3.0.28 or later fix pack.
  3. 3. For IBM MQ 9.4 LTS (9.4.0.0 through 9.4.0.10): Upgrade to 9.4.0.11 or later fix pack.
  4. 4. For IBM MQ 9.4 CD (9.3.0 through 9.4.2): Upgrade to 9.4.3 or later.
  5. 5. Download the appropriate fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral/).
  6. 6. Apply the upgrade following IBM MQ Appliance upgrade procedures in the IBM MQ documentation.
Caveat Standard IBM MQ upgrade considerations apply - review release notes for compatibility notes and ensure application compatibility before production deployment

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

Fix this in Mq Appliance Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
23.0 hours of engineering $4,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,528.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0975 — 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-0975 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