Aria OperationsApplication · VMware
CVE-2026-41723
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 · high confidenceVMware Cloud Foundation Operations contains multiple stored cross-site scripting vulnerabilities where authenticated users with privileges to create policies, views, or text-widgets can inject malicious JavaScript scripts that execute when other users view the content, potentially allowing administrative action execution.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 product and versionCheck the VMware product installed (Aria Operations, Cloud Foundation, Telco Cloud Platform, or vSphere) and determine the exact version number through the product's UI or command line interfaceAffected if The installed version falls within any of the affected ranges: Aria Operations >= 8.0 and < 8.18.7; Cloud Foundation >= 5.0 and < 8.18.7, >= 9.0 and < 9.0.2.0, or = 9.1; Telco Cloud Platform >= 5.0 and <= 5.1; vSphere >= 9.0 and < 9.0.2.0 or = 9.1
-
Verify user privilegesCheck if the current user account has permissions to create or edit policies, views, or text widgets within the product's administration interface or role-based access control settingsAffected if The user has privileges to create or modify policies, views, or text-widget components
-
Review existing policies for injected scriptsAccess the policies management section and inspect all custom policies for any unexpected script tags, JavaScript event handlers, or encoded characters that may contain malicious payloadAffected if Any policy contains unsanitized script content, especially script tags or javascript: URIs in policy name, description, or configuration fields
-
Review existing views for injected scriptsNavigate to the views or dashboards section and examine all custom views for suspicious script content in view names, descriptions, or configuration parametersAffected if Any view contains unsanitized script content, especially script tags or javascript: URIs in view configuration
-
Review text-widgets for injected scriptsExamine all text-widget or custom widget configurations in the environment for any script content embedded within text fieldsAffected if Any text-widget contains unsanitized script content, particularly in display text or linked resource fields
The environment is affected if the installed product version is within the affected ranges AND the user has creation privileges for policies, views, or text-widgets that may contain injected malicious scripts.
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
Implement strict input validation and contextual output encoding for all user-supplied content in policies, views, and text-widgets; apply Content Security Policy headers to mitigate XSS execution.
Aria Operations: 8.18.7+ | Cloud Foundation: 8.18.7+ (8.x) or 9.0.2.0+ (9.x) | vSphere: 9.0.2.0+
- Identify the specific VMware product from the affected list: Aria Operations, Cloud Foundation, Telco Cloud Platform, or vSphere
- Determine the current installed version of the product
- For Aria Operations: upgrade to version 8.18.7 or later
- For Cloud Foundation (8.x branch): upgrade to version 8.18.7 or later
- For Cloud Foundation (9.x branch): upgrade to version 9.0.2.0 or later
- For vSphere: upgrade to version 9.0.2.0 or later
- For Telco Cloud Platform: contact Broadcom support for upgrade path guidance as no fixed version is specified in the advisory
- After upgrade, verify the new version is running
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Aria Operations
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41723 — 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-41723 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