# CVE-2026-11726: IBM MQ for HPE NonStop is vulnerable to a denial of service issue

> An authenticated attacker can cause a denial of service or obtain sensitive information in IBM MQ for HPE NonStop due to improper validation of message header offsets.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-6r76-w3vq-7277

## What is CVE-2026-11726?

CVE-2026-11726 is a high-severity denial of service vulnerability in IBM MQ for HPE NonStop, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 could allow an authenticated attacker to obtain sensitive information or cause a denial of service due to improper validation of message header offset values.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-11726?


## How do I fix CVE-2026-11726?

No fix has been published for CVE-2026-11726 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11726 being exploited?

There is no known exploitation of CVE-2026-11726 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11726 and fix it if it is affected.

What it is: CVE-2026-11726 is a high-severity denial of service vulnerability in IBM MQ for HPE NonStop, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11726 in the wild and no public exploit code.

Affected product: IBM MQ for HPE NonStop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11726/ (Markdown: https://insights.sbomify.com/CVE-2026-11726/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11726
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11726
- OSV: https://osv.dev/vulnerability/CVE-2026-11726

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11726/
Summaries are generated and may contain mistakes; the official description above is the record.