# CVE-2026-22719: Broadcom VMware Aria Operations Command Injection

> Unauthenticated attackers can execute arbitrary commands during product migration, leading to remote code execution in VMware Aria Operations.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Mar 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-2hp7-6cr6-jvxh

## What is CVE-2026-22719?

CVE-2026-22719 is a high-severity command injection vulnerability in Vmware Cloud Foundation, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VMware Aria Operations contains a command injection vulnerability. A malicious unauthenticated actor may exploit this issue to execute arbitrary commands which may lead to remote code execution in VMware Aria Operations while support-assisted product migration is in progress. 

To remediate CVE-2026-22719, apply the patches listed in the 'Fixed Version' column of the ' Response Matrix https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36947 ' in VMSA-2026-0001 

Workarounds for CVE-2026-22719 are documented in the 'Workarounds' column of the ' Response Matrix https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36947 ' in VMSA-2026-0001

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 4 products.


Products: Vmware Aria Operations, Vmware Cloud Foundation, Vmware Telco Cloud Infrastructure, Vmware Telco Cloud Platform.

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

No fix has been published for CVE-2026-22719 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Mar 2026.

## Is CVE-2026-22719 being exploited?

Yes. Attackers have exploited CVE-2026-22719 in the wild since at least 3 Mar 2026.

## Other vulnerabilities in Vmware Cloud Foundation

- [CVE-2026-41722](https://insights.sbomify.com/CVE-2026-41722/): Cross-site scripting in VCF operations (high 8.0)
- [CVE-2026-41723](https://insights.sbomify.com/CVE-2026-41723/): Cross-site scripting in VCF operations (high 8.0)
- [CVE-2026-41724](https://insights.sbomify.com/CVE-2026-41724/): Cross-site scripting in VCF operations (high 8.0)
- [CVE-2026-22720](https://insights.sbomify.com/CVE-2026-22720/): VMware Aria Operations stored cross-site scripting vulnerability (high 8.0)
- [CVE-2024-38830](https://insights.sbomify.com/CVE-2024-38830/): Local privilege escalation vulnerability (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22719 is a high-severity command injection vulnerability in Vmware Cloud Foundation, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-22719 in the wild since at least 3 Mar 2026.

Affected product: Vmware Cloud Foundation. 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-22719/ (Markdown: https://insights.sbomify.com/CVE-2026-22719/index.md)
```

## Sources

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

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