en
Severity across 16 analyzed records
A short verification protects source data and prevents automated AI requests.
The GCVE catalog currently lists 145 vulnerability records affecting ESXi.
Among the 16 records analyzed by CyStack, 5 are High or Critical and 1 appear in the CISA KEV catalog.
Compare the version you run with each vulnerability and the provider guidance below. The data only includes records analyzed so far.
| CVE | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2025-41239vSockets information-disclosure vulnerability | Exploitation statusNot known exploited | FixYes | Published07/15/2025 | SeverityHigh |
CVE-2025-41238PVSCSI heap-overflow vulnerability | Exploitation statusNot known exploited | FixYes | Published07/15/2025 | SeverityCritical |
CVE-2025-41237VMCI integer-underflow vulnerability | Exploitation statusNot known exploited | FixYes | Published07/15/2025 | SeverityCritical |
CVE-2025-41236VMXNET3 integer-overflow vulnerability | Exploitation statusNot known exploited | FixYes | Published07/15/2025 | SeverityCritical |
CVE-2025-41228VMware ESXi and vCenter Server Reflected Cross Site Scripting (XSS) Vulnerability | Exploitation statusNot known exploited | FixYes | Published05/20/2025 | SeverityMedium |
CVE-2025-41227Denial-of-Service Vulnerability | Exploitation statusNot known exploited | FixYes | Published05/20/2025 | SeverityMedium |
CVE-2025-41226Guest Operations Denial-of-Service Vulnerability | Exploitation statusNot known exploited | FixYes | Published05/20/2025 | SeverityMedium |
CVE-2025-22226CVE-2025-22226 | Exploitation statusKEV | FixYes | Published03/04/2025 | SeverityHigh |
CVE-2025-22225CVE-2025-22225 | Exploitation statusKEV | FixYes | Published03/04/2025 | SeverityHigh |
CVE-2025-22224CVE-2025-22224 | Exploitation statusKEV | FixYes | Published03/04/2025 | SeverityCritical |
CVE-2024-37086CVE-2024-37086 | Exploitation statusNot known exploited | FixYes | Published06/25/2024 | SeverityMedium |
CVE-2024-37085CVE-2024-37085 | Exploitation statusKEV | FixYes | Published06/25/2024 | SeverityMedium |
CVE-2024-22273CVE-2024-22273 | Exploitation statusNot known exploited | FixYes | Published05/21/2024 | SeverityHigh |
CVE-2024-22255Information disclosure vulnerability | Exploitation statusNot known exploited | FixYes | Published03/05/2024 | SeverityHigh |
CVE-2024-22254Out-of-bounds write vulnerability | Exploitation statusNot known exploited | FixYes | Published03/05/2024 | SeverityHigh |
CVE-2024-22253Use-after-free vulnerability | Exploitation statusNot known exploited | FixYes | Published03/05/2024 | SeverityCritical |
CVE-2024-22252Use-after-free vulnerability | Exploitation statusNot known exploited | FixYes | Published03/05/2024 | SeverityCritical |
CVE-2023-29552CVE-2023-29552 | Exploitation statusKEV | FixNot confirmed | Published04/25/2023 | SeverityHigh |
CVE-2022-31705CVE-2022-31705 | Exploitation statusNot known exploited | FixNot confirmed | Published12/14/2022 | SeverityHigh |
CVE-2022-31699CVE-2022-31699 | Exploitation statusNot known exploited | FixNot confirmed | Published12/13/2022 | SeverityLow |
CVE-2022-31696CVE-2022-31696 | Exploitation statusNot known exploited | FixNot confirmed | Published12/13/2022 | SeverityHigh |
CVE-2022-31681CVE-2022-31681 | Exploitation statusNot confirmed | FixNot confirmed | Published10/07/2022 | SeverityUnknown |
CVE-2022-23825CVE-2022-23825 | Exploitation statusNot confirmed | FixNot confirmed | Published07/14/2022 | SeverityUnknown |
CVE-2022-29901Arbitrary Memory Disclosure through CPU Side-Channel Attacks (Retbleed) | Exploitation statusNot confirmed | FixNot confirmed | Published07/12/2022 | SeverityMedium |
CVE-2022-21166CVE-2022-21166 | Exploitation statusNot known exploited | FixNot confirmed | Published06/15/2022 | SeverityMedium |
CVE-2022-21125CVE-2022-21125 | Exploitation statusNot known exploited | FixNot confirmed | Published06/15/2022 | SeverityMedium |
CVE-2022-21123CVE-2022-21123 | Exploitation statusNot known exploited | FixNot confirmed | Published06/15/2022 | SeverityMedium |
CVE-2021-22050CVE-2021-22050 | Exploitation statusNot confirmed | FixNot confirmed | Published02/16/2022 | SeverityUnknown |
CVE-2021-22043CVE-2021-22043 | Exploitation statusNot confirmed | FixNot confirmed | Published02/16/2022 | SeverityUnknown |
CVE-2021-22041CVE-2021-22041 | Exploitation statusNot confirmed | FixNot confirmed | Published02/16/2022 | SeverityUnknown |
CVE-2021-22042CVE-2021-22042 | Exploitation statusNot confirmed | FixNot confirmed | Published02/16/2022 | SeverityUnknown |
CVE-2021-22040CVE-2021-22040 | Exploitation statusNot confirmed | FixNot confirmed | Published02/16/2022 | SeverityUnknown |
CVE-2021-22045CVE-2021-22045 | Exploitation statusNot confirmed | FixNot confirmed | Published01/04/2022 | SeverityUnknown |
CVE-2021-21995CVE-2021-21995 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-21994CVE-2021-21994 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-21974CVE-2021-21974 | Exploitation statusPublic exploit | FixNot confirmed | Published02/24/2021 | SeverityHigh |
CVE-2020-3999CVE-2020-3999 | Exploitation statusNot confirmed | FixNot confirmed | Published12/21/2020 | SeverityUnknown |
CVE-2020-4004CVE-2020-4004 | Exploitation statusNot confirmed | FixNot confirmed | Published11/20/2020 | SeverityUnknown |
CVE-2020-4005CVE-2020-4005 | Exploitation statusNot confirmed | FixNot confirmed | Published11/20/2020 | SeverityUnknown |
CVE-2020-3995CVE-2020-3995 | Exploitation statusNot confirmed | FixNot confirmed | Published10/20/2020 | SeverityUnknown |
CVE-2020-3992CVE-2020-3992 | Exploitation statusKEV | FixNot confirmed | Published10/20/2020 | SeverityCritical |
CVE-2020-3982CVE-2020-3982 | Exploitation statusNot confirmed | FixNot confirmed | Published10/20/2020 | SeverityUnknown |
CVE-2020-3981CVE-2020-3981 | Exploitation statusNot confirmed | FixNot confirmed | Published10/20/2020 | SeverityUnknown |
CVE-2020-3976CVE-2020-3976 | Exploitation statusNot confirmed | FixNot confirmed | Published08/21/2020 | SeverityUnknown |
CVE-2020-3971CVE-2020-3971 | Exploitation statusNot confirmed | FixNot confirmed | Published06/25/2020 | SeverityUnknown |
CVE-2020-3965CVE-2020-3965 | Exploitation statusNot confirmed | FixNot confirmed | Published06/25/2020 | SeverityUnknown |
CVE-2020-3964CVE-2020-3964 | Exploitation statusNot confirmed | FixNot confirmed | Published06/25/2020 | SeverityUnknown |
CVE-2020-3963CVE-2020-3963 | Exploitation statusNot confirmed | FixNot confirmed | Published06/25/2020 | SeverityUnknown |
CVE-2020-3966CVE-2020-3966 | Exploitation statusNot confirmed | FixNot confirmed | Published06/25/2020 | SeverityUnknown |
CVE-2020-3968CVE-2020-3968 | Exploitation statusNot confirmed | FixNot confirmed | Published06/25/2020 | SeverityUnknown |
CVE-2020-3967CVE-2020-3967 | Exploitation statusNot confirmed | FixNot confirmed | Published06/25/2020 | SeverityUnknown |
CVE-2020-3970CVE-2020-3970 | Exploitation statusNot confirmed | FixNot confirmed | Published06/25/2020 | SeverityUnknown |
CVE-2020-3962CVE-2020-3962 | Exploitation statusNot confirmed | FixNot confirmed | Published06/24/2020 | SeverityUnknown |
CVE-2020-3969CVE-2020-3969 | Exploitation statusNot confirmed | FixNot confirmed | Published06/24/2020 | SeverityUnknown |
CVE-2020-3959CVE-2020-3959 | Exploitation statusNot confirmed | FixNot confirmed | Published05/29/2020 | SeverityUnknown |
CVE-2020-3958CVE-2020-3958 | Exploitation statusNot confirmed | FixNot confirmed | Published05/29/2020 | SeverityUnknown |
CVE-2020-3955CVE-2020-3955 | Exploitation statusNot confirmed | FixNot confirmed | Published04/29/2020 | SeverityUnknown |
CVE-2019-5544CVE-2019-5544 | Exploitation statusKEV | FixNot confirmed | Published12/06/2019 | SeverityCritical |
CVE-2019-5536CVE-2019-5536 | Exploitation statusNot confirmed | FixNot confirmed | Published10/28/2019 | SeverityUnknown |
CVE-2019-5527CVE-2019-5527 | Exploitation statusNot confirmed | FixNot confirmed | Published10/10/2019 | SeverityUnknown |
CVE-2019-5521CVE-2019-5521 | Exploitation statusNot confirmed | FixNot confirmed | Published09/20/2019 | SeverityUnknown |
CVE-2019-5531CVE-2019-5531 | Exploitation statusNot confirmed | FixNot confirmed | Published09/18/2019 | SeverityUnknown |
CVE-2019-5528CVE-2019-5528 | Exploitation statusNot confirmed | FixNot confirmed | Published07/11/2019 | SeverityUnknown |
CVE-2019-5517CVE-2019-5517 | Exploitation statusNot confirmed | FixNot confirmed | Published04/15/2019 | SeverityUnknown |
CVE-2019-5520CVE-2019-5520 | Exploitation statusNot confirmed | FixNot confirmed | Published04/15/2019 | SeverityUnknown |
CVE-2019-5516CVE-2019-5516 | Exploitation statusNot confirmed | FixNot confirmed | Published04/15/2019 | SeverityUnknown |
CVE-2019-5518CVE-2019-5518 | Exploitation statusNot confirmed | FixNot confirmed | Published04/01/2019 | SeverityUnknown |
CVE-2019-5519CVE-2019-5519 | Exploitation statusNot confirmed | FixNot confirmed | Published04/01/2019 | SeverityUnknown |
CVE-2018-6981CVE-2018-6981 | Exploitation statusNot confirmed | FixNot confirmed | Published12/04/2018 | SeverityUnknown |
CVE-2018-6982CVE-2018-6982 | Exploitation statusNot confirmed | FixNot confirmed | Published12/04/2018 | SeverityUnknown |
CVE-2018-6974CVE-2018-6974 | Exploitation statusNot confirmed | FixNot confirmed | Published10/16/2018 | SeverityUnknown |
CVE-2018-6977CVE-2018-6977 | Exploitation statusNot confirmed | FixNot confirmed | Published10/09/2018 | SeverityUnknown |
CVE-2018-6972CVE-2018-6972 | Exploitation statusNot confirmed | FixNot confirmed | Published07/25/2018 | SeverityUnknown |
CVE-2018-6967CVE-2018-6967 | Exploitation statusNot confirmed | FixNot confirmed | Published07/09/2018 | SeverityUnknown |
CVE-2018-6965CVE-2018-6965 | Exploitation statusNot confirmed | FixNot confirmed | Published07/09/2018 | SeverityUnknown |
CVE-2018-6966CVE-2018-6966 | Exploitation statusNot confirmed | FixNot confirmed | Published07/09/2018 | SeverityUnknown |
CVE-2017-5753CVE-2017-5753 | Exploitation statusPublic exploit | FixNot confirmed | Published01/04/2018 | SeverityMedium |
CVE-2017-4940CVE-2017-4940 | Exploitation statusNot confirmed | FixNot confirmed | Published12/20/2017 | SeverityUnknown |
CVE-2017-4941CVE-2017-4941 | Exploitation statusNot confirmed | FixNot confirmed | Published12/20/2017 | SeverityUnknown |
CVE-2017-4933CVE-2017-4933 | Exploitation statusNot confirmed | FixNot confirmed | Published12/20/2017 | SeverityUnknown |
CVE-2017-16544CVE-2017-16544 | Exploitation statusNot known exploited | FixNot confirmed | Published11/20/2017 | SeverityHigh |
CVE-2017-4925CVE-2017-4925 | Exploitation statusNot confirmed | FixNot confirmed | Published09/15/2017 | SeverityUnknown |
CVE-2017-4924CVE-2017-4924 | Exploitation statusNot confirmed | FixNot confirmed | Published09/15/2017 | SeverityUnknown |
CVE-2017-4904CVE-2017-4904 | Exploitation statusNot confirmed | FixNot confirmed | Published06/07/2017 | SeverityUnknown |
CVE-2017-4902CVE-2017-4902 | Exploitation statusNot confirmed | FixNot confirmed | Published06/07/2017 | SeverityUnknown |
CVE-2017-4903CVE-2017-4903 | Exploitation statusNot confirmed | FixNot confirmed | Published06/07/2017 | SeverityUnknown |
CVE-2017-4905CVE-2017-4905 | Exploitation statusNot confirmed | FixNot confirmed | Published06/07/2017 | SeverityUnknown |
CVE-2016-7463CVE-2016-7463 | Exploitation statusNot confirmed | FixNot confirmed | Published12/29/2016 | SeverityUnknown |
CVE-2016-5330CVE-2016-5330 | Exploitation statusNot confirmed | FixNot confirmed | Published08/08/2016 | SeverityUnknown |
CVE-2016-5331CVE-2016-5331 | Exploitation statusNot confirmed | FixNot confirmed | Published08/08/2016 | SeverityUnknown |
CVE-2015-6933CVE-2015-6933 | Exploitation statusNot confirmed | FixNot confirmed | Published01/09/2016 | SeverityUnknown |
CVE-2014-8370CVE-2014-8370 | Exploitation statusNot confirmed | FixNot confirmed | Published01/29/2015 | SeverityUnknown |
CVE-2015-1044CVE-2015-1044 | Exploitation statusNot confirmed | FixNot confirmed | Published01/29/2015 | SeverityUnknown |
CVE-2014-4241CVE-2014-4241 | Exploitation statusNot confirmed | FixNot confirmed | Published07/17/2014 | SeverityUnknown |
CVE-2014-3793CVE-2014-3793 | Exploitation statusNot confirmed | FixNot confirmed | Published05/31/2014 | SeverityUnknown |
CVE-2014-1207CVE-2014-1207 | Exploitation statusNot confirmed | FixNot confirmed | Published01/17/2014 | SeverityUnknown |
CVE-2014-1208CVE-2014-1208 | Exploitation statusNot confirmed | FixNot confirmed | Published01/17/2014 | SeverityUnknown |
CVE-2013-3519CVE-2013-3519 | Exploitation statusNot confirmed | FixNot confirmed | Published12/04/2013 | SeverityUnknown |
CVE-2013-5970CVE-2013-5970 | Exploitation statusNot confirmed | FixNot confirmed | Published10/21/2013 | SeverityUnknown |
CVE-2013-3658CVE-2013-3658 | Exploitation statusNot confirmed | FixNot confirmed | Published09/10/2013 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
