CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighFixed-version data available

CVE-2026-22719 remediation guide

Broadcom VMware Aria Operations

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 th...

Open CVE record
ProductBroadcom VMware Aria Operations
Affected versions8.18.x, 9.0, 4.0, 2.0, >= 8.0 < 8.18.6, >= 4.0 < 5.2.3, >= 9.0 < 9.0.2.0, >= 2.2 <= 3.0, >= 4.0 <= 5.1
Fixed versions8.18.6, 5.2.3, 9.0.2.0
Priority basisImmediate · CVSS 8.1 · EPSS 17.4%
01

Identify the affected asset

Confirm whether Broadcom VMware Aria Operations is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 8.18.x, 9.0, 4.0, 2.0, >= 8.0 < 8.18.6, >= 4.0 < 5.2.3, >= 9.0 < 9.0.2.0, >= 2.2 <= 3.0, >= 4.0 <= 5.1. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

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

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.