IBM MQ queue manager is vulnerable to remote code execution

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps IBM/MQ (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for IBM/MQ.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 18, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 18, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 18, 2026

Sources and claim methodology

• Source referenceibm.com

Related CVEs

• Data deletion and attribute disclosure via field-name method injection in in-memory queriesAlso CWE-470
• Document deletion and process crash via unvalidated method-name dispatch in atomic pop operationAlso CWE-470
• LMDeploy has Remote Code Execution by Pickle Deserialization via handle_zmq_recv in lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.pySame generic ecosystem
• LMDeploy vulnerable to arbitrary code execution via eval() of untrusted quant_dtype in model config loadingSame generic ecosystem
• virtio-win: Integer overflow causing a heap overflow in Viosock driverSame generic ecosystem
• Rsyslog: Heap buffer overflow in imhttp plugin Basic Authentication handlingSame generic ecosystem