Skip to content
Noroxi
CVE-2020-4682· NVD / CVE Program· CNA ibm

IBM MQ 7.5, 8.0, 9.0, 9.1, 9.2 LTS, and 9.2 CD could allow a remote attacker to execute arbitrary code on the system, caused by an unsafe de

Noroxi assessment

Priority: Plan (action score 41/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 7.2% (FIRST EPSS); higher than 94.2% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to the record, no fixed version is available yet.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

IBM MQ 7.5, 8.0, 9.0, 9.1, 9.2 LTS, and 9.2 CD could allow a remote attacker to execute arbitrary code on the system, caused by an unsafe deserialization of trusted data. An attacker could exploit this vulnerability to execute arbitrary code on the system. IBM X-Force ID: 186509.

CriticalCVSS 9.8 · v3.1—No exploit No fix recorded
Published
Jan 28, 2021
Updated
Jun 16, 2026
EPSS
7.2% · 94th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

41

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 7.2%

CNA vs NVD score

NVD
9.8
CNA · ibm
8.1
1.7 point gap

CVSS:3.0/AC:H/I:H/S:U/C:H/UI:N/A:H/AV:N/PR:N/RL:O/RC:C/E:U

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

VendorProduct
ibmmq
ibmmq appliance
ibmwebsphere mq

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • ibm mq8.0.0.0
  • ibm mq8.0.0.1
  • ibm mq8.0.0.10
  • ibm mq8.0.0.11
  • ibm mq8.0.0.12
  • ibm mq8.0.0.13
  • ibm mq8.0.0.14
  • ibm mq8.0.0.15
  • ibm mq8.0.0.2
  • ibm mq8.0.0.3
  • ibm mq8.0.0.4
  • ibm mq8.0.0.5
  • ibm mq8.0.0.6
  • ibm mq8.0.0.7
  • ibm mq8.0.0.8
  • ibm mq8.0.0.9
  • ibm mq9.0.0.0
  • ibm mq9.0.0.1
  • ibm mq9.0.0.10
  • ibm mq9.0.0.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.

  • IBM MQ

    • 8.0.0, 9.0.0, 9.1.0, 7.5.0, 9.2.0affected

Same product

ibm: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-10027IBM MQ queue manager is vulnerable to unauthenticated remote code execution
    39Monitor
  • CVE-2026-12351IBM MQ is vulnerable to unauthenticated remote code execution via JNDI injection
    39Monitor
  • CVE-2022-22489IBM MQ 8.0, (9.0, 9.1, 9.2 LTS), and (9.1 and 9.2 CD) are vulnerable to an XML External Entity Injection (XXE) attack when processing XML da
    37Monitor
  • CVE-2026-11725IBM MQ queue manager is vulnerable to privilege escalation
    35Monitor
  • CVE-2026-11378IBM MQ queue manager is vulnerable to remote code execution
    35Monitor
  • CVE-2026-11375IBM MQ queue manager is vulnerable to remote code execution
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python
payload = sock.recv(65536)job = pickle.loads(payload)

Fixed

python
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig):    raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records