CVE-2024-37085: VMware ESXi · Authentication bypass vulnerability
Affects VMware ESXiSource CVE Database V5
Exploited in the wild · used in ransomware campaigns · KEV due 20 Aug 2024 · 26% EPSS : apply the vendor's fix or mitigations to VMware ESXi now.
Data as of 26 Oct 2026, 06:26 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else.
- Ransomware
- Used in ransomware campaigns
- EPSS
- 26.7% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 25 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 35 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by vmware
, 22 days before disclosure
CVE published
on cve.org
, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed · ransomware use known
, 35 days after disclosure
KEV remediation due
US federal deadline
, 56 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| VMware VMware ESXi | Affected
| Fixed in– |
Description
VMware ESXi contains an authentication bypass vulnerability. A malicious actor with sufficient Active Directory (AD) permissions can gain full access to an ESXi host that was previously configured to use AD for user management https://blogs.vmware.com/vsphere/2012/09/joining-vsphere-hosts-to-active-directory.html by re-creating the configured AD group ('ESXi Admins' by default) after it was deleted from AD.