# CVE-2026-11847: Integration Corp｜iVEC-IEI Virtualization Edge Computer - Arbitrary File Deletion

> Authenticated attackers can exploit a path traversal flaw to create directories in unintended system paths on IEI Integration Corp edge computers.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-6f9h-v5v9-qmr3

## What is CVE-2026-11847?

CVE-2026-11847 is a medium-severity path traversal vulnerability in IEI Integration Corp iVEC TANK-XM811, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The 
 iVEC-IEI Virtualization Edge Computer developed by IEI Integration Corp has a Path Traversal vulnerability, allowing authenticated remote attackers to exploit this vulnerability to create directories in unintended system paths.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-11847 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11847 is a medium-severity path traversal vulnerability in IEI Integration Corp iVEC TANK-XM811, published on 12 Jun 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-11847 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-11847/ (Markdown: https://insights.sbomify.com/CVE-2026-11847/index.md)
```

## Sources

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

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