CVE-2026-22719
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVMware 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVMware Aria Operations contains a command injection vulnerability that allows an unauthenticated attacker to execute arbitrary commands, potentially achieving remote code execution. The vulnerability is specifically exploitable during support-assisted product migration operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 8.0, < 8.18.6>= 4.0, < 5.2.3>= 9.0, < 9.0.2.0>= 2.2, <= 3.0>= 4.0, <= 5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed VMware product and versionLocate the product version through the management interface, about page, or product-specific command (such as 'vmsa-support --version' or checking the /opt/vmware directory structure). Common paths include /usr/lib/vmware-caf/env/CAF_INstallation_Version or the vami_config backup logs.Affected if The installed version falls within any of these ranges: Aria Operations >= 8.0 to < 8.18.6, Cloud Foundation >= 4.0 to < 5.2.3 or >= 9.0 to < 9.0.2.0, Telco Cloud Infrastructure >= 2.2 to <= 3.0, or Telco Cloud Platform >= 4.0 to <= 5.1
-
Determine if support-assisted migration is configuredCheck the product configuration for migration-related settings. Look for migration wizard state files, backup/restore configurations that include migration options, or support bundle configurations that enable remote assistance.Affected if Support-assisted product migration features or wizards have been accessed, configured, or left in an active state on the system
-
Verify network exposure of management interfacesReview firewall rules, access controls, and network binding configurations for the management interface (typically port 443/8443). Check if the Appliance Management or Admin interfaces are accessible from untrusted networks.Affected if The management interface is accessible to unauthenticated network attackers without proper network segmentation or VPN protection
You are affected if your installed product version is within the affected ranges AND the support-assisted migration feature is or was accessible, particularly from untrusted networks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.2.38.18.69.0.2.0
Apply the patches listed in the VMSA-2026-0001 Response Matrix for CVE-2026-22719. If immediate patching is not feasible, implement the documented workarounds from the same Response Matrix.
Upgrade to the fixed version specified in VMSA-2026-0001 Response Matrix (e.g., Aria Operations 8.18.6+, Cloud Foundation 5.2.3+/9.0.2.0+)
- 1. Identify your specific VMware product and current version from the affected list (Aria Operations, Cloud Foundation, Telco Cloud Infrastructure, or Telco Cloud Platform)
- 2. Access the VMSA-2026-0001 Response Matrix at https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36947
- 3. Locate the 'Fixed Version' column for your product in the Response Matrix
- 4. Upgrade to the fixed version specified in the matrix for your product line (e.g., Aria Operations to 8.18.6+, Cloud Foundation to 5.2.3+/9.0.2.0+, Telco Cloud Infrastructure to version above 3.0, Telco Cloud Platform to version above 5.1)
- 5. If immediate upgrade is not possible, consult the 'Workarounds' column in the same Response Matrix for mitigation steps
- 6. After applying the fix, verify the remediation by confirming the product version matches the fixed version listed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22719 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22719 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data