Skip to main content
Mallory
HighVulnerability

CVE-2025-41225: Authenticated command execution in VMware vCenter Server

Published May 20, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS0.26%18th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2025-41225CWE-78 · Improper Neutralization of Special…

CVE-2025-41225 is an authenticated command-execution vulnerability in VMware vCenter Server. According to the provided content and VMware advisory references, a malicious actor with privileges to create or modify alarms and to run script actions can exploit the issue to execute arbitrary commands on the vCenter Server management plane. The available material does not identify the specific vulnerable function or code path, only that exploitation is tied to vCenter alarm/script-action functionality.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary command execution on the vCenter Server. Because vCenter is the central management plane for VMware environments, compromise can affect the confidentiality, integrity, and availability of the management system and may enable broader administrative abuse within the virtual infrastructure. The provided content assigns a CVSSv3 base score of 8.8.

Mitigation

If you can’t patch tonight, do this now.

The provided content states that VMware reported no workarounds are available for CVE-2025-41225. Practical risk reduction prior to patching is therefore limited to restricting and auditing privileges related to creating or modifying alarms and running script actions, minimizing access to vCenter administrative functions, and accelerating patch deployment; however, the vendor-stated corrective action is upgrading to a fixed version.

Remediation

Patch, then assume compromise.

Apply VMware/Broadcom security updates addressing VMSA-2025-0010. The provided content states that VMware vCenter Server 8.0 is fixed in version 8.0 U3e and VMware vCenter Server 7.0 is fixed in version 7.0 U3v. For VMware Cloud Foundation deployments that include affected vCenter versions, apply the asynchronous patches mapped to vCenter 8.0 U3e or 7.0 U3v as documented by VMware/Broadcom.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-41225 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-41225 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-41225?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-41225.
Is there a patch for CVE-2025-41225?
Apply VMware/Broadcom security updates addressing VMSA-2025-0010. The provided content states that VMware vCenter Server 8.0 is fixed in version 8.0 U3e and VMware vCenter Server 7.0 is fixed in version 7.0 U3v.
How severe is CVE-2025-41225?
CVE-2025-41225 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.26% (18th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.