What is CVE-2021-22054?

CVE-2021-22054 is Omnissa Workspace ONE Server-Side Request Forgery. The supplied enrichment data classifies it as SSRF mapped to CWE-918 Server-Side Request Forgery (SSRF).

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

21 public PoC repositories reported; 2 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, cloud metadata access logs, egress proxy logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2021-22054 using CVSS 7.5, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighSSRFpublic exploit

CVE-2021-22054

CVE-2021-22054 — Omnissa Workspace ONE Server-Side Request Forgery

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2021-22054 in CISA KEV with required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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.

Published Dec 17, 2021Updated Jun 17, 2026Sources: NVD, Omnissa (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Mar 9, 2026

EPSS

100%

top of FIRST's scoreset

Affects

Omnissa

VMware Workspace ONE UEM console

CVSS base

7.5

high · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade VMware Workspace ONE UEM console to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Federal deadline Mar 23, 2026 — passed 195 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Omnissa	VMware Workspace ONE UEM console	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.	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.5	CVSS 3.1	high	3.9	3.6	NVD, CNA
5	CVSS 2.0	medium	10	2.9	NVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-918 · Server-Side Request Forgery (SSRF)

Read Application Data
Execute Unauthorized Code or Commands::

Weakness & attack patterns

CWE-918Server-Side Request Forgery (SSRF)

Inferred from the weakness class — not observed against this CVE.

CAPEC-664 · Server Side Request Forgery

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Mar 9, 2026

Federal deadline

Mar 23, 2026

passed 195 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

7 more posts on this CVEShowing 5 of 12 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable VMware Workspace ONE UEM console.
Monitor for scanner or exploit-pattern traffic after 21 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPScloud metadata access logsegress proxy logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.5 (AV:N)
Jun 17, 2026 · NVD
Added to CISA KEV catalog
Mar 9, 2026 · CISA
2024
CVE is exploited. "k0mi-tg/CVE-POC"
Feb 1, 2024 · SOCRadar CTI
2023
CVE is exploited. "ARPSyndicate/cvemon"
Dec 5, 2023 · SOCRadar CTI
CVE is exploited. "WhooAmii/POC_to_review"
Dec 5, 2023 · SOCRadar CTI
CVE is exploited. "manas3c/CVE-POC"
Dec 5, 2023 · SOCRadar CTI
CVE is exploited. "nomi-sec/PoC-in-GitHub"
Dec 5, 2023 · SOCRadar CTI
2021
Initial · CVE published
Dec 17, 2021 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

9×TweetsFeb 12, 2023 – Jun 12, 2026 · SOCRadar CTI
9×SVRS was changedMar 11, 2026 – Apr 16, 2026 · SOCRadar CTI
6×Github ReposJun 3, 2022 – Dec 5, 2023 · SOCRadar CTI
1×CVE modified by NIST: CISA KEV details updated.Mar 23, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Mar 10, 2026 · SOCRadar CTI
1×2 times mentioned on 2 Telegram channelsMar 10, 2026 · SOCRadar CTI

References

5 on the record

www.vmware.com/security/advisories/VMSA-2021-0029.html
Patch, Vendor Advisory, MITRE_REFERENCES
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-22054
US Government Resource, NIST
www.greynoise.io/blog/new-ssrf-exploitation-surge
Third Party Advisory, NIST
web.archive.org/web/20211222154335/https://www.vmware.com/security/advisories/VMSA-2021-0029.html
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2021-22054
Vendor Advisory

Coverage

7 stories from the feeds we poll

2 more reports on this CVEShowing 5 of 7 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Omnissaevery CVE for this vendor
March 2026what else CISA listed
SSRFsame class
CWE-918other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2021-22054 is Omnissa Workspace ONE Server-Side Request Forgery, a high vulnerability affecting VMware Workspace ONE UEM console from Omnissa. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 21 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.5 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.