# CVE-2026-17133: IBM App Connect Enterprise Toolkit is vulnerable to arbitrary code execution due to multiple CVEs

> A local attacker can execute arbitrary code on IBM App Connect Enterprise Toolkit due to improper neutralization of special elements in OS commands.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-gghq-hpvc-v3rx

## What is CVE-2026-17133?

CVE-2026-17133 is a high-severity command injection vulnerability in IBM App Connect Enterprise, published on 14 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

IBM App Connect Enterprise 13.0.1.0 through 13.0.8.0, and 12.0.1.0 through 12.0.12.27 could allow a local attacker to execute arbitrary code due to improper neutralization of special elements used in an OS command.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-17133 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17133 is a high-severity command injection vulnerability in IBM App Connect Enterprise, published on 14 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-17133 in the wild and no public exploit code.

Affected product: IBM App Connect Enterprise. 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-17133/ (Markdown: https://insights.sbomify.com/CVE-2026-17133/index.md)
```

## Sources

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

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