# CVE-2021-22005: VMware vCenter Server File Upload

> Attackers can upload malicious files to vCenter Server via the Analytics service to execute arbitrary code remotely.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2021
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-9w75-994h-2j26

## What is CVE-2021-22005?

CVE-2021-22005 is a critical vulnerability in Vmware Cloud Foundation, published on 23 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The vCenter Server contains an arbitrary file upload vulnerability in the Analytics service. A malicious actor with network access to port 443 on vCenter Server may exploit this issue to execute code on vCenter Server by uploading a specially crafted file.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2021-22005?

It affects 2 products.


Products: Vmware Cloud Foundation, Vmware Vcenter Server.

## How do I fix CVE-2021-22005?

No fix has been published for CVE-2021-22005 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 17 Nov 2021.

## Is CVE-2021-22005 being exploited?

Yes. Attackers have exploited CVE-2021-22005 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Public exploit code:

- https://github.com/shmilylty/cve-2021-22005-exp (github_poc): https://github.com/shmilylty/cve-2021-22005-exp
- https://github.com/rwincey/CVE-2021-22005 (github_poc): https://github.com/rwincey/CVE-2021-22005
- the metasploit script(POC/EXP) about CVE-2021-22005 VMware vCenter Server contains an arbitrary file upload vulnerability (github_poc): https://github.com/TaroballzChen/CVE-2021-22005-metasploit
- VMware vCenter Server任意文件上传漏洞 / Code By:Jun_sheng (github_poc): https://github.com/Jun-5heng/CVE-2021-22005
- CVE-2021-22005批量验证python脚本 (github_poc): https://github.com/5gstudent/CVE-2021-22005-
- https://github.com/1ZRR4H/CVE-2021-22005 (github_poc): https://github.com/1ZRR4H/CVE-2021-22005

## Other vulnerabilities in Vmware Cloud Foundation

- [CVE-2024-38812](https://insights.sbomify.com/CVE-2024-38812/): VMware vCenter Server Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-37079](https://insights.sbomify.com/CVE-2024-37079/): Broadcom VMware vCenter Server Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2022-22954](https://insights.sbomify.com/CVE-2022-22954/): VMware Workspace ONE Access and Identity Manager Server-Side Template Injection (critical 9.8, exploited in the wild)
- [CVE-2021-21985](https://insights.sbomify.com/CVE-2021-21985/): VMware vCenter Server Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2021-21975](https://insights.sbomify.com/CVE-2021-21975/): VMware Server Side Request Forgery in vRealize Operations Manager API (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22005 and fix it if it is affected.

What it is: CVE-2021-22005 is a critical vulnerability in Vmware Cloud Foundation, published on 23 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2021-22005 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

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-2021-22005/ (Markdown: https://insights.sbomify.com/CVE-2021-22005/index.md)
```

## Sources

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

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