# CVE-2025-41241: Denial-of-service vulnerability

> Authenticated attackers with specific API permissions can trigger a denial-of-service condition in VMware vCenter.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2025
- **Updated:** 29 Jul 2025
- **Also known as:** GHSA-w9mx-hpxm-qx9w

## What is CVE-2025-41241?

CVE-2025-41241 is a medium-severity denial of service vulnerability in VMware Cloud Foundation, published on 29 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

VMware vCenter contains a denial-of-service vulnerability. A malicious actor who is authenticated through vCenter and has permission to perform API calls for guest OS customisation may trigger this vulnerability to create a denial-of-service condition.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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


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

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

## Is CVE-2025-41241 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41241 is a medium-severity denial of service vulnerability in VMware Cloud Foundation, published on 29 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41241 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-41241/ (Markdown: https://insights.sbomify.com/CVE-2025-41241/index.md)
```

## Sources

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

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