Menu

Star on GitHub · 3.4k

CVE-2026-10853

7.5 · HIGH

IBM MQ could allow an authenticated attacker with cluster access to cause a denial of service or potentially execute arbitrary code due to improper validation of cluster command message lengths.

Published Sep 18, 2026ibmCWE-470EPSS 0.55%

Overview

CVE-2026-10853 is a high-severity vulnerability affecting ibm mq. It was published on September 18, 2026 and has a CVSS 3.1 base score of 7.5 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.5, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

IBM MQ could allow an authenticated attacker with cluster access to cause a denial of service or potentially execute arbitrary code due to improper validation of cluster command message lengths.

Remediation

Check the references section for vendor advisories and patches from ibm. Update mq to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus
ibmmq9.1.0.0Affected

Frequently asked questions

What is CVE-2026-10853?

CVE-2026-10853 is a high-severity vulnerability affecting ibm mq. It was published on September 18, 2026 and has a CVSS 3.1 base score of 7.5 (HIGH).

How severe is CVE-2026-10853?

This vulnerability has a CVSS 3.1 base score of 7.5, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-10853?

Check the references section for vendor advisories and patches from ibm. Update mq to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-10853?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-10853 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Watch the demo →