# CVE-2025-41225: VMware vCenter Server authenticated command-execution vulnerability

> Authenticated attackers with alarm modification privileges can execute arbitrary commands on VMware vCenter Server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-2687-xwfr-5fx9

## What is CVE-2025-41225?

CVE-2025-41225 is a high-severity command injection vulnerability in VMware Cloud Foundation, published on 20 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The vCenter Server contains an authenticated command-execution vulnerability. A malicious actor with privileges to create or modify alarms and run script action may exploit this issue to run arbitrary commands on the vCenter Server.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-41225?


## How do I fix CVE-2025-41225?

No fix has been published for CVE-2025-41225 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-41225 being exploited?

There is no known exploitation of CVE-2025-41225 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41225 and fix it if it is affected.

What it is: CVE-2025-41225 is a high-severity command injection vulnerability in VMware Cloud Foundation, published on 20 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41225 in the wild and no public exploit code.

Affected product: VMware Cloud Foundation. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-41225/ (Markdown: https://insights.sbomify.com/CVE-2025-41225/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-41225
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-41225
- OSV: https://osv.dev/vulnerability/CVE-2025-41225

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-41225/
Summaries are generated and may contain mistakes; the official description above is the record.