IBM MQ for HPE NonStop up to 8.1.0.40 Cluster Migration input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.3 | $5k-$25k | 0.40 |
Summary
A vulnerability identified as very critical has been detected in IBM MQ for HPE NonStop up to 8.1.0.40. This affects an unknown part of the component Cluster Migration. The manipulation leads to input validation. This vulnerability is uniquely identified as CVE-2026-11716. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in IBM MQ for HPE NonStop up to 8.1.0.40. It has been rated as very critical. This issue affects some unknown functionality of the component Cluster Migration. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 could allow an authenticated attacker to cause a denial of service or potentially execute arbitrary code during queue manager startup due to improper validation of cluster migration data.
The advisory is shared at ibm.com. The identification of this vulnerability is CVE-2026-11716 since 06/09/2026. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are required for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/18/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 8.1.0.0
- 8.1.0.1
- 8.1.0.2
- 8.1.0.3
- 8.1.0.4
- 8.1.0.5
- 8.1.0.6
- 8.1.0.7
- 8.1.0.8
- 8.1.0.9
- 8.1.0.10
- 8.1.0.11
- 8.1.0.12
- 8.1.0.13
- 8.1.0.14
- 8.1.0.15
- 8.1.0.16
- 8.1.0.17
- 8.1.0.18
- 8.1.0.19
- 8.1.0.20
- 8.1.0.21
- 8.1.0.22
- 8.1.0.23
- 8.1.0.24
- 8.1.0.25
- 8.1.0.26
- 8.1.0.27
- 8.1.0.28
- 8.1.0.29
- 8.1.0.30
- 8.1.0.31
- 8.1.0.32
- 8.1.0.33
- 8.1.0.34
- 8.1.0.35
- 8.1.0.36
- 8.1.0.37
- 8.1.0.38
- 8.1.0.39
- 8.1.0.40
License
Website
- Vendor: https://www.ibm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.3VulDB Meta Temp Score: 8.3
VulDB Base Score: 9.1
VulDB Temp Score: 9.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (ibm): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/09/2026 CVE reserved09/18/2026 Advisory disclosed
09/18/2026 VulDB entry created
09/18/2026 VulDB entry last update
Sources
Vendor: ibm.comAdvisory: ibm.com
Status: Confirmed
CVE: CVE-2026-11716 (🔒)
GCVE (CVE): GCVE-0-2026-11716
GCVE (VulDB): GCVE-100-407717
Entry
Created: 09/18/2026 21:35Changes: 09/18/2026 21:35 (62)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.