CVE-2024-37085
An authority record changed. This is a change in what is asserted about exploitation, not in how the vulnerability is described.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- CISA requires: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. The federal deadline has passed: overdue since 2024-08-20. CISA KEVCISA's notes for this entry: support.broadcom.com
- Upgrade to cloud foundation 5.2 or later upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
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.
- weakness
- Authentication bypass vulnerability
- affected
- n/a VMware ESXi; n/a VMware Cloud Foundation
- published ranges
- vmware cloud foundation >= 4.0 < 5.2; vmware esxi 7.0; vmware esxi 8.0; vmware esxi 8.0-a; and 9 more on the CVE page
- first unaffected version, by branch
- cloud foundation 5.2
- severity
- 6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
- assigned by
- vmware
- published
- 2024-06-25
check us support.broadcom.com
Authority held, dated
- CISA KEV
- listed
- added
- 2024-07-30
- remediation due
- 2024-08-20
- ransomware use
- known
- remediation status
- overdue since 2024-08-20
- exploit code
- 3 public proof-of-concept repositories, first seen 2024-08-02 (PoC-in-GitHub).
A KEV listing is an assertion of observed exploitation. It is the only element on this page that makes that claim.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 26 Jun 2024 | 0.00043 | |
| 31 Jul 2024 | 0.01179 | |
| 1 Aug 2024 | 0.00306 | |
| 3 Aug 2024 | 0.0122 | |
| 17 Mar 2025 | 0.76063 | crossed 0.10, crossed 0.50 · scoring model v2025.03.14 |
| 10 Jun 2026 | 0.80269 | |
| 15 Jun 2026 | 0.2677 | crossed 0.50 · scoring model v2026.06.15 |
| 24 Jul 2026 | 0.25952 | |
| 28 Aug 2026 | 0.2677 |
67 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Listed, added 2024-07-30. Due 2024-08-20. A changed deadline or a change in ransomware use changes this brief.
- exploit probability
- 0.27 on 2026-08-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 50% (0.50). Crossing a line changes this brief.
- fix
- Held: cloud foundation 5.2. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2024-37085', '2026-10-29T23:59:59.999999Z', now());