The vCenter Server contains an SSRF (Server Side Request Forgery) vulnerability due to improper validation of URLs in vCenter Server Conten…

published 2021-09-23 5y ago modified 2026-06-17 4mo ago also EUVD-2021-9164

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 61%
public exploits: 0; none known

The vCenter Server contains an SSRF (Server Side Request Forgery) vulnerability due to improper validation of URLs in vCenter Server Content Library. An authorised user with access to content library may exploit this issue by sending a POST request to vCenter Server leading to information disclosure.

Patch / fix

fixed in 1 links 1

vmware cloud_foundation 5.0

vmware.com/security/advisories/VMSA-2021-0020.html advisory

Is CVE-2021-21993 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.94% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected products

n/a VMware vCenter Server, VMware Cloud Foundation

Classification

Weakness

CWE-918 Server-Side Request Forgery

Technology feeds

VMware rss critical rss

References

vmware.com /security/advisories/VMSA-2021-0020.html
patch, vendor-advisory

Sources

CVE List CVE-2021-21993
NVD CVE-2021-21993

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.