# CVE-2026-11845: IEI Integration Corp｜iVEC-IEI Virtualization Edge Computer - OS Command Injection

> Privileged remote attackers can inject and execute arbitrary OS commands on IEI Integration Corp iVEC Virtualization Edge Computer devices.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-xvpv-jmc6-72gq

## What is CVE-2026-11845?

CVE-2026-11845 is a high-severity command injection vulnerability in IEI Integration Corp iVEC TANK-XM811, published on 12 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The iVEC-IEI Virtualization Edge Computer developed by IEI Integration Corp has a OS Command Injection vulnerability, allowing privileged remote attackers to inject arbitrary OS commands and execute them on the device.

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

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


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

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

## Is CVE-2026-11845 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11845 is a high-severity command injection vulnerability in IEI Integration Corp iVEC TANK-XM811, published on 12 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11845 in the wild and no public exploit code.

Affected product: IEI Integration Corp iVEC TANK-XM811. 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-11845/ (Markdown: https://insights.sbomify.com/CVE-2026-11845/index.md)
```

## Sources

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

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