# CVE-2021-21975: VMware Server Side Request Forgery in vRealize Operations Manager API

> Attackers with network access can exploit SSRF in the API to steal administrative credentials, requiring an upgrade to vRealize Operations Manager.

- **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 18 Jan 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2021
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-px27-325w-m34c

## What is CVE-2021-21975?

CVE-2021-21975 is a critical server-side request forgery vulnerability in Vmware Cloud Foundation, published on 31 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Server Side Request Forgery in vRealize Operations Manager API (CVE-2021-21975) prior to 8.4 may allow a malicious actor with network access to the vRealize Operations Manager API can perform a Server Side Request Forgery attack to steal administrative credentials.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 3 products.


Products: Vmware Cloud Foundation, Vmware Vrealize Operations Manager, Vmware Vrealize Suite Lifecycle Manager.

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

No fix has been published for CVE-2021-21975 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 1 Feb 2022.

## Is CVE-2021-21975 being exploited?

Yes. Attackers have exploited CVE-2021-21975 in the wild since at least 18 Jan 2022, including in ransomware campaigns.

Public exploit code:

- vRealize RCE + Privesc (CVE-2021-21975, CVE-2021-21983, CVE-0DAY-?????) (github_poc): https://github.com/rabidwh0re/REALITY_SMASHER
- Nmap script to check vulnerability CVE-2021-21975 (github_poc): https://github.com/GuayoyoCyber/CVE-2021-21975
- CVE-2021-21975 vRealize Operations Manager SSRF (github_poc): https://github.com/Al1ex/CVE-2021-21975
- VMWare vRealize SSRF-CVE-2021-21975 (github_poc): https://github.com/Henry4E36/VMWare-vRealize-SSRF
- [CVE-2021-21975] VMware vRealize Operations Manager API Server Side Request Forgery (SSRF) (github_poc): https://github.com/murataydemir/CVE-2021-21975
- VMWare-CVE-2021-21975 SSRF vulnerability (github_poc): https://github.com/Vulnmachines/VMWare-CVE-2021-21975

## 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-22005](https://insights.sbomify.com/CVE-2021-22005/): VMware vCenter Server File Upload (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-21975 is a critical server-side request forgery vulnerability in Vmware Cloud Foundation, published on 31 Mar 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-21975 in the wild since at least 18 Jan 2022, 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-21975/ (Markdown: https://insights.sbomify.com/CVE-2021-21975/index.md)
```

## Sources

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

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