CVE-2021-22054
VMware Workspace ONE UEM console 20.0.8 prior to 20.0.8.37, 20.11.0 prior to 20.11.0.40, 21.2.0 prior to 21.2.0.27, and 21.5.0 prior to 21.5.0.37 contain an SSRF vulnerability. This issue may allow a malicious actor with network access to UEM to send their requests without authentication and to gain access to sensitive information.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. SSRF makes the server call a URL the attacker picks. A WAF can block well-known targets such as cloud metadata addresses, but not every internal host.
Also consider: egress filter · IMDSv2
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2021-22054 being exploited?
Yes. CVE-2021-22054 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2021-22054?
CVE-2021-22054 is rated High with a CVSS score of 7.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2021-22054?
Yes. A fix has been recorded for CVE-2021-22054. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2021-22054 affect?
CVE-2021-22054 affects vmware:workspace_one_uem_console. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affectedVMware Workspace ONE UEM console 20.0.8 prior to 20.0.8.37, 20.11.0 prior to 20.11.0.40, 21.2.0 prior to 21.2.0.27, and 21.5.0 prior to 21.5.0.37.
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept · 1 Nuclei template
- VMWare Workspace ONE UEM - Server-Side Request Forgery · detection template · high
- MKSx/CVE-2021-22054 · 5 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 11 Mar 2026 (SSVC 2.0.3).
timeline
- 17 Dec 2021Published
- 3 Jun 2022First proof-of-concept repository on GitHub (unvetted) · 167 days (about 6 months) later
- 9 Mar 2026Added to CISA KEV (exploited in the wild) · 1,375 days (about 4 years) later
- 11 Mar 2026CISA SSVC assessment: exploitation active · 2 days later
- 23 Mar 2026CISA remediation due date (US federal agencies) · 12 days later
- 1 Oct 2026CVE record last updated · 193 days (about 6 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 32 days later
- Advisorygreynoise.io /blog/new-ssrf-exploitation-surge
- Linkvmware.com /security/advisories/VMSA-2021-0029.html
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-22054
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.