Automated Threat Modeling

VMware Cloud Foundation Operations CVE-2026-41723: Overview of Stored XSS Enabling Administrative Hijacking

CVE-2026-41723 is a stored cross-site scripting vulnerability in VMware Cloud Foundation Operations that lets low-privileged users inject persistent scripts and hijack administrative sessions. This post covers the patch and the affected versions.

CVE Analysis

10 min read

ZeroPath CVE Analysis
ZeroPath CVE Analysis

2026-06-08

VMware Cloud Foundation Operations CVE-2026-41723: Overview of Stored XSS Enabling Administrative Hijacking
Experimental AI-Generated Content

This CVE analysis is an experimental publication that is completely AI-generated. The content may contain errors or inaccuracies and is subject to change as more information becomes available. We are continuously refining our process.

If you have feedback, questions, or notice any errors, please reach out to us.

[email protected]

Introduction

Three stored cross-site scripting vulnerabilities in VMware Cloud Foundation Operations, disclosed together in VMSA-2026-0004, allow a low-privileged authenticated user to inject persistent scripts that execute administrative actions when a higher-privileged user views them. CVE-2026-41723 is one of the three. It lands in a product family where a related command injection flaw, CVE-2026-22719, was actively exploited within 30 days of its disclosure earlier this year. That history makes the urgency of patching concrete.

Technical Information

Root Cause: Insufficient Input Sanitization

CVE-2026-41723 is a stored cross-site scripting vulnerability. VMware Cloud Foundation Operations does not properly sanitize user-supplied input in three distinct creation workflows: policies, views, and text-widgets. When an authenticated user with privileges to create any of these elements submits content containing JavaScript, the application stores the payload without adequate encoding or filtering. The browser of any later user who views the affected dashboard element then renders the malicious content verbatim.

The CVSSv3.1 vector string is AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, which gives a base score of 8.0. Each component says something about the attack surface:

CVSS ComponentValueImplication
Attack VectorNetwork (AV:N)Exploitable remotely over the network
Attack ComplexityLow (AC:L)No specialized conditions required
Privileges RequiredLow (PR:L)Attacker needs only basic policy/widget creation rights
User InteractionRequired (UI:R)Victim must access the compromised dashboard element
ScopeUnchanged (S:U)Impact confined to the vulnerable component
ConfidentialityHigh (C:H)Full access to sensitive data possible
IntegrityHigh (I:H)Data modification at administrative level possible
AvailabilityHigh (A:H)Service disruption achievable

Why Stored XSS Matters Here

The "stored" classification is what makes this a serious threat. Unlike a reflected XSS payload, this one persists in the application database, and every user who views the affected policy, view, or text-widget runs the script. A single injection becomes a sustained attack vector that can hijack the administrative sessions of multiple victims without the attacker having to act again.

Attack Flow

A realistic exploitation chain looks like this:

  1. A low-privileged operator (or a compromised account with operator-level access) creates a policy, view, or text-widget containing embedded JavaScript. The application accepts and stores the payload because its input validation is insufficient.

  2. An administrator opens the dashboard containing the poisoned element during routine work. Normal dashboard viewing satisfies the user interaction requirement (UI:R), so the attacker needs no social engineering beyond standard operations.

  3. The injected script runs in the administrator's browser with their session token and full session privileges.

  4. The script can perform any administrative action available through the VCF Operations web interface. That includes modifying cloud infrastructure configurations, accessing sensitive operational data, creating new administrative accounts, and planting more persistent backdoors in other dashboard elements.

  5. With the hijacked admin session, the attacker can create more poisoned widgets or policies, so the attack can spread across the management interface and establish multiple persistence points.

Three Sibling Vulnerabilities

CVE-2026-41723 is one of three stored XSS flaws disclosed in VMSA-2026-0004. All three have identical CVSS vectors and descriptions and differ in the specific injection point:

CVE IDCVSSFixed in Aria Operations
CVE-2026-417228.08.18.6 and 8.18.7
CVE-2026-417238.08.18.6 and 8.18.7
CVE-2026-417248.08.18.7 only

Three distinct injection points with identical characteristics in one advisory strongly suggest a systemic input sanitization deficiency rather than isolated coding errors. VMSA-2026-0001 supports that reading. Published four months earlier, in February 2026, it addressed CVE-2026-22720, another stored XSS flaw in the same product family, which allowed script injection through custom benchmark definitions.

Convergence of Risk Factors

Three factors make CVE-2026-41723 more significant than its standalone CVSS score:

  1. XSS keeps recurring. Two advisories in four months indicate a codebase-wide sanitization problem, which means additional undiscovered XSS vectors likely exist.
  2. The Aria/VCF Operations stack is a confirmed active target. CVE-2026-22719 reached CISA KEV status within 30 days of disclosure.
  3. VCF Operations manages the entire virtualized infrastructure layer. Administrative actions compromised through XSS can affect VM deployment, network configuration, and storage allocation across the enterprise.

Patch Information

Broadcom addressed CVE-2026-41723 on June 8, 2026, in security advisory VMSA-2026-0004, which bundles fixes for all three related stored XSS vulnerabilities. Broadcom confirmed that this flaw has no workarounds. The only remediation path is the vendor-supplied update.

The fix sanitizes user-supplied input in the policy, view, and text-widget creation workflows so that injected script payloads are no longer stored or rendered.

The complete remediation matrix:

ProductAffected VersionsFixed VersionNotes
VCF Operations9.1.x.x9.1.0.0Full fix for all three CVEs
VCF Operations9.0.x.x9.0.2.0 EP2Full fix for all three CVEs
VMware Aria Operations8.x8.18.6Partial: CVE-2026-41722 and CVE-2026-41723 only
VMware Aria Operations8.x8.18.7Full fix for all three CVEs
VMware Cloud Foundation 5.x5.xAria Operations 8.18.7Component-level fix
VMware Telco Cloud Platform 5.x5.xPer KB443138Broadcom KB article

VMware Aria Operations version 8.18.6 remediates CVE-2026-41723 and CVE-2026-41722 but does not address CVE-2026-41724. Only version 8.18.7 covers all three CVEs. Organizations running the standalone Aria Operations product should upgrade directly to 8.18.7 to close all three issues in a single update cycle.

Downloads for each fixed release are available through the Broadcom Support Portal.

Interim Risk Reduction

Patching is the only complete fix. Based on the documented prerequisites, these measures reduce the attack surface until you can patch:

  • Limit policy, view, and text-widget creation to the minimum set of essential administrative roles. This directly shrinks the pool of accounts an attacker could use for injection.
  • Review administrative dashboard access and modification logs for anomalous content, particularly unexpected JavaScript or HTML tags in policies, views, or text-widgets.
  • Configure web application firewall (WAF) rules to detect common XSS payload patterns in HTTP requests targeting VCF Operations endpoints. These rules give only partial coverage against evasion techniques.
  • If the deployment architecture permits, enforce Content Security Policy (CSP) headers on VCF Operations web interfaces to limit script execution contexts.

Affected Systems and Versions

The following products and version ranges are confirmed affected:

  • VMware Cloud Foundation Operations (VCF Operations) versions 9.1.x.x and 9.0.x.x
  • VMware Aria Operations version 8.x (all 8.x releases before 8.18.6 for CVE-2026-41723 specifically, and before 8.18.7 for complete coverage of all three sibling CVEs)
  • VMware Cloud Foundation version 5.x (via the Aria Operations component)
  • VMware vSphere Foundation (via the VCF Operations component)
  • VMware Telco Cloud Platform version 5.x (via the Aria Operations component)

Any environment running these products with users who have privileges to create policies, views, or text-widgets is vulnerable.

Vendor Security History

Broadcom's VMware product line has had a sustained run of critical vulnerabilities over the past 18 months:

TimelineAdvisoryKey CVEsSeverityExploitation Status
March 2025VMSA-2025-0004CVE-2025-22224, CVE-2025-22225, CVE-2025-22226CriticalActively exploited zero-days; added to CISA KEV
February 2026VMSA-2026-0001CVE-2026-22719 (RCE), CVE-2026-22720 (XSS), CVE-2026-22721 (privesc)CVSS 8.1, 8.0, 7.8CVE-2026-22719 actively exploited; CISA KEV March 2026
June 2026VMSA-2026-0004CVE-2026-41722, CVE-2026-41723, CVE-2026-41724CVSS 8.0 eachNo confirmed exploitation as of publication

Microsoft Threat Intelligence Center reported the March 2025 zero-days. They involved a TOCTOU race condition (CVE-2025-22224) that could allow attackers with administrative access to seize hypervisor control and break out of guest OS sandboxes.

Stored XSS has now turned up in the same product family in both VMSA-2026-0001 and VMSA-2026-0004, four months apart. That recurrence signals a systemic input sanitization deficiency rather than isolated bugs. Organizations should consider a code-level audit of all user-input rendering paths in VCF Operations beyond the three patched locations.

Broadcom's security disclosure practices have also drawn scrutiny. Security researchers have noted that Broadcom failed to adequately disclose the scope of active exploitation in a timely manner for prior VMware zero-days. That has led to recommendations that organizations supplement Broadcom advisories with independent threat intelligence sources and CISA KEV monitoring.

Alexis Bernazzani of Visa Inc. privately reported the three CVEs in VMSA-2026-0004, following responsible disclosure practices.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization