CVE-2021-21985

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild
9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: >99.9%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2021 — use a compensating control (WAF / firewall / segmentation) and check the vendor's advisory.

The vSphere Client (HTML5) contains a remote code execution vulnerability due to lack of input validation in the Virtual SAN Health Check plug-in which is enabled by default in vCenter Server. A malicious actor with network access to port 443 may exploit this issue to execute commands with unrestricted privileges on the underlying operating system that hosts vCenter Server.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2021. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and check the vendor's advisory for a fix.
EPSS PROB
>99.9%
EPSS %ILE
99th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

No fix has been recorded since the CVE record was published in 2021. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and check the vendor's advisory for a fix.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2021-21985

Published

May 26, 2021

Last Modified

August 12, 2026

Advisory Details (4)

Auto-updated Oct 7, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record since 2021. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-21985
Web page

Support Content Notification - Support Portal - Broadcom support portal

https://www.vmware.com/security/advisories/VMSA-2021-0010.html
Web page

Packet Storm

http://packetstormsecurity.com/files/163487/VMware-vCenter-Server-Virtual-SAN-Health-Check-Remote-Code-Execution.html
Web page

Packet Storm

http://packetstormsecurity.com/files/162812/VMware-Security-Advisory-2021-0010.html

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 43× in last 7d / 204× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 925 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 825 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 07:52 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-12 19:24 UTCEG score recompute
  3. 2026-10-12 05:42 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-12 01:54 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-11 22:10 UTCEG score recompute
  6. 2026-10-11 22:10 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-11 18:26 UTCEG score recompute
  8. 2026-10-11 18:26 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-11 14:39 UTCEG score recompute
  10. 2026-10-11 14:39 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-11 10:55 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-11 07:11 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-11 03:27 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-10 23:42 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-10 19:58 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-10 16:14 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-10 12:28 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-10 08:45 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-10 04:59 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-10 01:15 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-09 21:29 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-09 17:44 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-09 14:00 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-09 10:14 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-09 06:25 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-09 02:39 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-08 22:55 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-08 19:11 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-08 15:25 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-08 11:41 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-08 07:56 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-08 04:11 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-08 00:26 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-07 20:42 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-07 16:58 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-07 13:12 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-07 09:28 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-07 05:44 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-07 02:00 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-06 22:16 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-06 18:32 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-06 14:48 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-06 11:04 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-06 07:20 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-06 03:36 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-05 23:51 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-05 20:08 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-05 16:23 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-05 12:40 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-05 08:55 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-05 05:09 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-05 01:25 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-04 21:41 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-04 17:57 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-04 14:08 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-04 10:23 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-04 06:38 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-04 02:54 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-03 23:11 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-03 19:25 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-03 15:41 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-03 11:56 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-03 08:11 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-03 04:26 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-03 00:42 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-02 20:58 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-02 17:14 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-02 13:29 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-02 09:44 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-02 06:00 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-02 02:15 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-01 22:27 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-01 18:41 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-01 14:55 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-01 11:11 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-01 07:27 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-01 03:43 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-09-30 23:59 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-09-30 20:12 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-09-30 16:28 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-09-30 12:43 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-09-30 08:59 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-09-30 05:15 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-09-30 01:29 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-09-29 21:45 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-09-29 18:00 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-29 14:11 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-09-29 10:27 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-29 06:41 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-09-29 02:57 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-28 23:12 UTCEG score recompute
  67. 2026-09-28 23:12 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-09-28 19:24 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-09-28 15:38 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-28 11:54 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-09-28 08:10 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-28 04:26 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-09-28 00:42 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-09-27 21:51 UTCCISA KEV update
  75. 2026-09-27 20:58 UTCGHSA enrichmentGHSA-rg6m-2r9v-c5fj · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(8 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 5 GitHub PoCs), as are 1 Nuclei detection template, 1 GitHub checker repository. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. No fix has been recorded since the CVE record was published in 2021. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system.

  • Metasploitexploit/linux/http/vmware_vcenter_vsan_health_rce✓ verified
    Published Jul 12, 2021

    VMware vCenter Server Virtual SAN Health Check Plugin RCE

    Open source ↗
  • GitHub PoCsknux/CVE-2021-21985_PoC
    Published Nov 9, 2021

    VMWARE VCENTER SERVER VIRTUAL SAN HEALTH CHECK PLUG-IN RCE (CVE-2021-21985)

    Open source ↗
  • GitHub PoCtestanull/Project_CVE-2021-21985_PoC
    Published Jun 5, 2021
    Open source ↗
  • GitHub PoCdaedalus/CVE-2021-21985
    Published Jun 4, 2021

    CVE-2021-21985 vmware 6.7-9.8 RCE

    Open source ↗
  • GitHub PoCxnianq/cve-2021-21985_exp
    Published Jun 3, 2021

    cve-2021-21985 exploit

    Open source ↗
  • GitHub checkeronSec-fr/CVE-2021-21985-Checker
    Published Jun 1, 2021

    CVE-2021-21985 Checker.

    Open source ↗
  • Nucleihttp/cves/2021/CVE-2021-21985.yaml
    Published May 31, 2021

    VMware vSphere Client (HTML5) - Remote Code Execution

    Open source ↗
  • GitHub PoCalt3kx/CVE-2021-21985_PoC
    Published May 29, 2021
    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2021-21985?
CVE-2021-21985 is a critical-severity vulnerability; its CVE record was published on May 26, 2021. The vSphere Client (HTML5) contains a remote code execution vulnerability due to lack of input validation in the Virtual SAN Health Check plug-in which is enabled by default in vCenter Server. A malicious actor with network access to port 443 may exploit this issue to execute commands with…
When was the CVE record for CVE-2021-21985 published?
The CVE record for CVE-2021-21985 was published on May 26, 2021. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 12, 2026; the record at its source may have been updated since.
Is CVE-2021-21985 actively exploited?
Yes. CISA added CVE-2021-21985 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting VMware vCenter Server. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix has been recorded since the CVE record was published in 2021. Restrict network exposure of the affected system or apply the vendor's mitigation, and check the vendor's advisory for a fix.
What is the CVSS score of CVE-2021-21985?
CVE-2021-21985 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2021-21985?
CVE-2021-21985 affects VMware vCenter Server.
How do I remediate CVE-2021-21985?
No fix for CVE-2021-21985 has been recorded since its CVE record was published in 2021. Restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and check the vendor's advisory for a fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2021-21985

Explore →

Is Your Infrastructure Affected by CVE-2021-21985?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs