Skip to content
Server Security Center
KEVhigh8.1

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

Broadcom VMware Aria Operations · listed in the CISA catalog of actively exploited vulnerabilities since 2026-03-03.

CVSS v3.1 (CVE record)
8.1
high
EPSS (exploit probability, 30 days)
18%
higher than 97.2% of all CVEs
Added to CISA KEV
2026-03-03
US federal due date 2026-03-24
Automatable (CISA SSVC)
no
technical impact: total

CVE-2026-22719 explained

CVE-2026-22719 is a command injection vulnerability in Broadcom VMware Aria Operations and related VMware products. An unauthenticated attacker may execute arbitrary commands, potentially leading to remote code execution, while support-assisted product migration is in progress. CISA lists it as known to be exploited.

Impact

A remote, unauthenticated attacker can run arbitrary commands, which may lead to remote code execution, but only while a support-assisted product migration is in progress. No user interaction is needed. Attack complexity is high. CISA rates the technical impact as total, meaning full control of the affected component, but not automatable. Confidentiality, integrity and availability impacts are all high. Attackers are known to use this vulnerability.

Who is affected

VMware Aria Operations 8.18.x up to but not including 8.18.6. VMware Cloud Foundation Operations from 4.0 up to but not including 5.2.3, and from 9.0 up to but not including 9.0.2. VMware Telco Cloud Platform and VMware Telco Cloud Infrastructure from 2.0 up to but not including 5.2.3. The CVE record names no fixed version. Fixed versions are listed in the 'Fixed Version' column of the Response Matrix in VMSA-2026-0001.

Written with AI from the data on this page and checked against it automatically.

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 support.broadcom.com/web/ecx/support-content-notification… ' in VMSA-2026-0001 Workarounds for CVE-2026-22719 are documented in the 'Workarounds' column of the ' Response Matrix support.broadcom.com/web/ecx/support-content-notification… ' in VMSA-2026-0001

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • VMware Aria Operations
    Affected
    • 8.18.x, < 8.18.6
    Fixed in
    not stated
  • VMware Cloud Foundation Operations
    Affected
    • ≥ 4.0, < 5.2.3
    • ≥ 9.0, < 9.0.2
    Fixed in
    not stated
  • VMware Telco Cloud Platform
    Affected
    • ≥ 2.0, < 5.2.3
    Fixed in
    not stated
  • VMware Telco Cloud Infrastructure
    Affected
    • ≥ 2.0, < 5.2.3
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: support.broadcom.com/web/ecx/support-content-notification…
  • CISA's deadline for US federal agencies: 2026-03-24 (passed) – a useful benchmark for everyone else, too.

Vendor solution:

Workaround: Workarounds are available and documented by the vendor (see VMSA-2026-0001 KB430349) knowledge.broadcom.com/external/article/430349 for environments where immediate patching is not possible.

What to do

  1. Identify all VMware Aria Operations, Cloud Foundation Operations, Telco Cloud Platform and Telco Cloud Infrastructure deployments in the affected version ranges.
  2. Apply the patches listed in the 'Fixed Version' column of the Response Matrix in VMSA-2026-0001.
  3. If you cannot patch immediately, apply the workarounds in the 'Workarounds' column of the same Response Matrix.
  4. Restrict network access to these systems, especially during support-assisted product migration.
  5. Check affected systems for signs of compromise, since the vulnerability is known to be exploited.
  6. If mitigations are unavailable, follow CISA's required action and discontinue use of the product.

The CVE record names no fixed version. Use the 'Fixed Version' and 'Workarounds' columns of the Response Matrix in VMSA-2026-0001 to find patches or workarounds. CISA requires applying mitigations per vendor instructions, following BOD 22-01 guidance for cloud services, or discontinuing use of the product if mitigations are unavailable. Limit network exposure in the meantime.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

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

Questions about CVE-2026-22719

Is my system exposed at all times?
According to the description, exploitation can lead to remote code execution while support-assisted product migration is in progress. Patch or apply the vendor workarounds regardless, because the vulnerability is known to be exploited.
Does an attacker need credentials?
No. The description states that a malicious unauthenticated actor may exploit the issue, and no user interaction is required. Attack complexity is rated high.
Is there a deadline for remediation?
CISA added CVE-2026-22719 to its Known Exploited Vulnerabilities catalog on 2026-03-03, with a due date of 2026-03-24 for US federal agencies.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.