# CVE-2025-41250: Header injection vulnerability

> A malicious actor with limited privileges can manipulate SMTP headers in vCenter notification emails, potentially altering email content or metadata.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-5qfp-g44c-j8xm

## What is CVE-2025-41250?

CVE-2025-41250 is a high-severity vulnerability in VMware Cloud Foundation, published on 29 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

VMware vCenter contains an SMTP header injection vulnerability. A malicious actor with non-administrative privileges on vCenter who has permission to create scheduled tasks may be able to manipulate the notification emails sent for scheduled tasks.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2025-41250 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41250 is a high-severity vulnerability in VMware Cloud Foundation, published on 29 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41250 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-41250/ (Markdown: https://insights.sbomify.com/CVE-2025-41250/index.md)
```

## Sources

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

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