Aria OperationsApplication · VMware
CVE-2026-41722
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 Cloud Foundation Operations contains multiple stored cross-site scripting vulnerabilities.A malicious actor with privileges to create policies, views or text-widgets may be able to inject scripts to perform administrative actions in VMware Cloud Foundation Operations.
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 · moderate confidenceVMware Cloud Foundation Operations contains stored cross-site scripting vulnerabilities where authenticated users with privileges to create policies, views, or text-widgets can inject malicious JavaScript scripts. These scripts execute in the browsers of other users viewing the crafted content, potentially allowing the attacker to perform administrative actions.
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
Aria OperationsApplication
>= 8.0, < 8.18.7
Cloud FoundationApplication
>= 5.0, < 8.18.7>= 9.0, < 9.0.2.0= 9.1
Telco Cloud PlatformApplication
>= 5.0, <= 5.1
VsphereApplication
>= 9.0, < 9.0.2.0= 9.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
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 versionUse the product's web UI or command line to determine the exact version number. For VMware Aria Operations, check /opt/vmware/vcf/ops/ or use the product UI under Administration > System Settings. For VMware Cloud Foundation, check the SDDC Manager interface. For VMware Vsphere, check the vCenter Server About page.Affected if The installed version falls within any of these ranges: Aria Operations >= 8.0 to < 8.18.7; Cloud Foundation >= 5.0 to < 8.18.7, >= 9.0 to < 9.0.2.0, or = 9.1; Telco Cloud Platform >= 5.0 to <= 5.1; Vsphere >= 9.0 to < 9.0.2.0 or = 9.1
-
Determine if policies, views, or text-widgets are accessibleLog into the product interface and navigate to the sections for creating policies, custom views, or text-widgets. For VMware Aria Operations, check under the Dashboards or Views sections. For Cloud Foundation, check the Operations dashboard customization features.Affected if The product allows authenticated users to create or edit policies, views, or text-widgets. This is the attack surface for the XSS vulnerability.
-
Check if users have elevated privileges for content creationReview the user roles and permissions in the product's Administration or Access Control settings. Identify which roles grant privileges to create policies, views, or text-widgets.Affected if There exist user accounts with privileges to create policies, views, or text-widgets, or if any non-admin user has been granted these capabilities. The vulnerability requires an authenticated attacker with these specific privileges.
-
Inspect existing policies, views, and text-widgets for suspicious contentExamine the content of existing policies, custom views, and text-widgets in the application for any unexpected script tags, JavaScript event handlers, or encoded payloads that may indicate prior exploitation.Affected if Any policies, views, or text-widgets contain script tags, javascript: URIs, or other potentially malicious script injection payloads.
A user is affected if they are running any of the listed product versions AND the policies, views, or text-widgets features are accessible to authenticated users with content creation privileges.
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 · scoped8.18.79.0.2.0
Apply VMware security patches when available; implement strict input validation and output encoding for all user-supplied content in policies, views, and text-widgets; audit existing content for malicious scripts.
Upgrade to 8.18.7 (for Aria Operations/Cloud Foundation 5.x-8.x) or 9.0.2.0 (for Cloud Foundation/Vsphere 9.x); Telco Cloud Platform requires vendor confirmation
- 1. Identify the specific affected product (Aria Operations, Cloud Foundation, Telco Cloud Platform, or Vsphere) in your environment
- 2. Determine the current version of the installed product
- 3. For Aria Operations: Upgrade to version 8.18.7 or later
- 4. For Cloud Foundation: Upgrade to version 8.18.7 (for 5.x/8.x releases) or 9.0.2.0 or later (for 9.x releases)
- 5. For Vsphere: Upgrade to version 9.0.2.0 or later
- 6. For Telco Cloud Platform: Contact Broadcom support for the specific fixed release as version 5.1 is the maximum listed
- 7. After upgrade, verify the XSS vulnerability is remediated by testing policy, view, and text-widget creation with script payloads
- 8. Review user permissions to ensure only trusted users have privileges to create policies, views, or text-widgets
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Aria Operations
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41722 — 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-41722 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