CVE-2024-37079
Broadcom VMware vCenter Server Out-of-bounds Write Vulnerability
Broadcom VMware vCenter Server
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 23 January 2026. US federal agencies were required to remediate it by 13 February 2026.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 22.4%, which is higher than 97.7% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2024-37079 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2024-37079.
What does CVE-2024-37079 affect?
CVE-2024-37079 affects Broadcom VMware vCenter Server. 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.
How severe is CVE-2024-37079?
CVE-2024-37079 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 22.4%, higher than 97.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 13 February 2026.
How should organisations respond to CVE-2024-37079?
Apply the vendor patch for Broadcom VMware vCenter Server as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.