# CVE-2026-8051: Command injection in Virtual Traffic Manager

> Remote authenticated admin can execute arbitrary OS commands on Ivanti Virtual Traffic Manager, requiring an upgrade to mitigate.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-3rm6-879f-q3r2

## What is CVE-2026-8051?

CVE-2026-8051 is a high-severity command injection vulnerability in ivanti Virtual Traffic Manager, published on 12 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

OS command injection in Ivanti Virtual Traffic Manager before version 22.9r4 allows a remote authenticated attacker with admin privileges to achieve remote code execution.

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

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

It affects 1 product.


Products: Ivanti Virtual Traffic Manager.

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

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

## Is CVE-2026-8051 being exploited?

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

## Other vulnerabilities in ivanti Virtual Traffic Manager

- [CVE-2024-7593](https://insights.sbomify.com/CVE-2024-7593/): Ivanti Virtual Traffic Manager Authentication Bypass (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8051 is a high-severity command injection vulnerability in ivanti Virtual Traffic Manager, published on 12 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8051 in the wild and no public exploit code.

Affected product: ivanti Virtual Traffic Manager. 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-8051/ (Markdown: https://insights.sbomify.com/CVE-2026-8051/index.md)
```

## Sources

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

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