CVE-2024-37079: Broadcom VMware vCenter Server · Heap-overflow vulnerability
Affects Broadcom VMware vCenter ServerSource CVE Database V5
Exploited in the wild · KEV due 13 Feb 2026 · 22% EPSS : apply the vendor's fix or mitigations to Broadcom VMware vCenter Server 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.
- EPSS
- 22.3% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 18 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 1.6 years 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
, 15 days before disclosure
CVE published
on cve.org
, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
, 1.6 years after disclosure
KEV remediation due
US federal deadline
, 1.7 years 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, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Vmwarevmware/vcenter-serverpkg:rpm/vmware/vcenter-serverOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
vCenter Server contains a heap-overflow vulnerability in the implementation of the DCERPC protocol. A malicious actor with network access to vCenter Server may trigger this vulnerability by sending a specially crafted network packet potentially leading to remote code execution.