How severe is CVE-2021-21975?

CVE-2021-21975 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2021-21975?

Affected package information for CVE-2021-21975 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2021-21975?

No patch has shipped for CVE-2021-21975 yet — track the vmware cloud foundation advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2021-21975 across my infrastructure?

Inventory every vmware cloud foundation deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2021-21975 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2021-21975?

O3 detects and blocks CVE-2021-21975 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2021-21975 actively exploited in the wild?

Yes. There are 19 known exploit references for CVE-2021-21975, including 13 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-21975?

CVE-2021-21975 has an EPSS (Exploit Prediction Scoring System) score of 78.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2021-21975 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2021-21975 (VMware Server Side Request Forgery in vRealize Operations Manager API) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-01-18. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-02-01. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2021-21975?

CVE-2021-21975 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2021-21975?

CVE-2021-21975 affects vmware cloud foundation (15 versions, e.g. 3.0, 3.0.1, 3.0.1.1…); vmware vrealize operations manager (8 versions, e.g. 7.0.0, 7.5.0, 8.0.0…); vmware vrealize suite lifecycle manager (4 versions, e.g. 8.0, 8.0.1, 8.1…). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2021-21975?

A Nuclei detection template exists for CVE-2021-21975, meaning automated scanners can fingerprint it. 2 Metasploit modules reference CVE-2021-21975, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2021-21975 published, and has it been updated?

CVE-2021-21975 was published on March 31, 2021 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-01-18 — agencies required to remediate by 2022-02-01 · Ransomware

CVE-2021-21975

HIGH

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…

Published

Mar 31, 2021

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

19 known

EPSS Exploitation Probability

via FIRST.org ↗

78.3%probability of exploitation in next 30 days

Very High Risk100th percentile-0.14%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

3 products · 27 configurations

Application

cloud foundationvmware

15 versions

3.03.0.13.0.1.13.53.5.13.73.7.13.7.23.83.8.13.93.9.1

Application

vrealize operations managervmware

8 versions

7.0.07.5.08.0.08.0.18.1.08.1.18.2.08.3.0

Application

vrealize suite lifecycle managervmware

4 versions

8.08.0.18.18.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.