dbcve.org
Aria OperationsApplication · VMware

CVE-2026-41724

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-08
Fix available
A fix is available. Upgrade to 8.18.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
VMware 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 confidence

VMware Cloud Foundation Operations contains multiple stored cross-site scripting vulnerabilities. Authenticated users with privileges to create policies, views, or text-widgets can inject malicious scripts that persists in the application and may allow execution of administrative actions.

MitigationApply VMware security patches when available. Until then, restrict privileges for policy/view/text-widget creation to minimally-privileged users and implement Content Security Policy headers to mitigate XSS 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
Affected:>= 8.0, < 8.18.7
Cloud FoundationApplication
Affected:>= 5.0, < 8.18.7
Telco Cloud PlatformApplication
Affected:>= 5.0, < 8.18.7

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product and version
    Access the VMware product administrative interface or use the command line to determine which product (VMware Aria Operations, VMware Cloud Foundation, or VMware Telco Cloud Platform) is running and its exact version number
    Affected if The product is one of the three affected products and the version is 8.0 or higher but below 8.18.7
  2. Confirm user access to policies, views, or text-widgets
    Check user account permissions within the product administrative console to determine if the current or any user account has privileges to create or edit policies, views, or text-widgets
    Affected if Any user account has create or edit privileges for policies, views, or text-widgets and the product version is vulnerable
  3. Review existing policies for injected scripts
    Navigate to the policies management section and inspect the configuration of existing policies, looking for any unusual script tags, JavaScript event handlers, or encoded content in policy fields
    Affected if Any policy contains suspicious script tags or JavaScript code that was not intentionally created by an administrator
  4. Review existing views and text-widgets for injected scripts
    Navigate to the views and text-widgets management sections and inspect their configurations for any suspicious script tags, event handlers, or unexpected HTML/JavaScript content
    Affected if Any view or text-widget contains suspicious script tags or JavaScript code that was not intentionally created by an administrator

A user is affected if they are running a vulnerable version (8.0 to 8.18.6) of VMware Aria Operations, VMware Cloud Foundation, or VMware Telco Cloud Platform and have users with privileges to create policies, views, or text-widgets, or if suspicious script content is found in existing policies, views, or text-widgets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.18.7 or later
Fixed in 8.18.7
Interim mitigation

Apply VMware security patches when available. Until then, restrict privileges for policy/view/text-widget creation to minimally-privileged users and implement Content Security Policy headers to mitigate XSS execution.

Recommended fix Moderate confidence

8.18.7

  1. Review the VMware Aria Operations 8.18.7 release notes to understand new features, resolved issues, and any prerequisites
  2. Ensure all system requirements for version 8.18.7 are met, including compatibility checks with your infrastructure
  3. Create a full backup of the current Aria Operations, Cloud Foundation, or Telco Cloud Platform configuration and database
  4. Schedule a maintenance window to perform the upgrade with minimal service disruption
  5. Upgrade Aria Operations to version 8.18.7 (or the equivalent update for Cloud Foundation/Telco Cloud Platform)
  6. After upgrade, verify that all services are running correctly and the web interface is accessible
  7. Validate that the XSS vulnerability is remediated by confirming the patch is applied and reviewing release notes for the security fix
Caveat Review release notes for potential compatibility changes or feature modifications when upgrading to 8.18.7

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41724 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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