en
Severity across 43 analyzed records
A short verification protects source data and prevents automated AI requests.
The GCVE catalog currently lists 226 vulnerability records affecting Workstation.
Among the 43 records analyzed by CyStack, 7 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-2026-41703Out-of-bounds read vulnerability | Exploitation statusNot known exploited | FixYes | Published07/30/2026 | SeverityHigh |
CVE-2026-22717VMware Workstation out-of-bound read vulnerability | Exploitation statusNot known exploited | FixYes | Published02/27/2026 | SeverityLow |
CVE-2026-22716VMware Workstation out-of-bounds write vulnerability | Exploitation statusNot known exploited | FixYes | Published02/27/2026 | SeverityMedium |
CVE-2026-22722VMware Workstation for Windows null pointer dereference may allow an authenticated user to trigger a crash | Exploitation statusNot known exploited | FixYes | Published02/26/2026 | SeverityMedium |
CVE-2026-22715VMware Workstation/Fusion NAT vulnerability | Exploitation statusNot known exploited | FixYes | Published02/26/2026 | SeverityMedium |
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-41227Denial-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-22224CVE-2025-22224 | Exploitation statusKEV | FixYes | Published03/04/2025 | SeverityCritical |
CVE-2024-22273CVE-2024-22273 | Exploitation statusNot known exploited | FixYes | Published05/21/2024 | SeverityHigh |
CVE-2024-22270CVE-2024-22270 | Exploitation statusNot known exploited | FixYes | Published05/14/2024 | SeverityHigh |
CVE-2024-22269CVE-2024-22269 | Exploitation statusNot known exploited | FixYes | Published05/14/2024 | SeverityHigh |
CVE-2024-22268CVE-2024-22268 | Exploitation statusNot known exploited | FixYes | Published05/14/2024 | SeverityHigh |
CVE-2024-22267CVE-2024-22267 | Exploitation statusNot known exploited | FixYes | Published05/14/2024 | SeverityCritical |
CVE-2024-22255Information disclosure 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-2024-22251Out-of-bounds read vulnerability | Exploitation statusNot known exploited | FixYes | Published02/27/2024 | SeverityMedium |
CVE-2023-34044Information disclosure vulnerability in bluetooth device-sharing functionality | Exploitation statusNot confirmed | FixYes | Published10/20/2023 | SeverityHigh |
CVE-2023-20869CVE-2023-20869 | Exploitation statusNot known exploited | FixNot confirmed | Published04/25/2023 | SeverityHigh |
CVE-2023-20870CVE-2023-20870 | Exploitation statusNot known exploited | FixNot confirmed | Published04/25/2023 | SeverityMedium |
CVE-2023-20872CVE-2023-20872 | Exploitation statusNot known exploited | FixNot confirmed | Published04/25/2023 | SeverityHigh |
CVE-2023-20854CVE-2023-20854 | Exploitation statusNot known exploited | FixNot confirmed | Published02/03/2023 | SeverityHigh |
CVE-2022-31705CVE-2022-31705 | Exploitation statusNot known exploited | FixNot confirmed | Published12/14/2022 | SeverityHigh |
CVE-2022-22983CVE-2022-22983 | Exploitation statusNot confirmed | FixNot confirmed | Published08/09/2022 | SeverityUnknown |
CVE-2021-22041CVE-2021-22041 | Exploitation statusNot confirmed | FixNot confirmed | Published02/16/2022 | SeverityUnknown |
CVE-2022-22938CVE-2022-22938 | Exploitation statusNot confirmed | FixNot confirmed | Published01/28/2022 | SeverityUnknown |
CVE-2021-22045CVE-2021-22045 | Exploitation statusNot confirmed | FixNot confirmed | Published01/04/2022 | SeverityUnknown |
CVE-2020-3960CVE-2020-3960 | Exploitation statusNot confirmed | FixNot confirmed | Published09/15/2021 | SeverityUnknown |
CVE-2021-21989CVE-2021-21989 | Exploitation statusNot confirmed | FixNot confirmed | Published05/24/2021 | SeverityUnknown |
CVE-2021-21988CVE-2021-21988 | Exploitation statusNot confirmed | FixNot confirmed | Published05/24/2021 | SeverityUnknown |
CVE-2021-21987CVE-2021-21987 | Exploitation statusNot confirmed | FixNot confirmed | Published05/24/2021 | SeverityUnknown |
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-3995CVE-2020-3995 | Exploitation statusNot confirmed | FixNot confirmed | Published10/20/2020 | SeverityUnknown |
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-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-3951CVE-2020-3951 | Exploitation statusNot confirmed | FixNot confirmed | Published03/17/2020 | SeverityUnknown |
CVE-2019-5543CVE-2019-5543 | Exploitation statusNot confirmed | FixNot confirmed | Published03/16/2020 | SeverityUnknown |
CVE-2020-3947CVE-2020-3947 | Exploitation statusNot confirmed | FixNot confirmed | Published03/16/2020 | SeverityUnknown |
CVE-2020-3948CVE-2020-3948 | Exploitation statusNot confirmed | FixNot confirmed | Published03/16/2020 | SeverityUnknown |
CVE-2019-5539CVE-2019-5539 | Exploitation statusNot confirmed | FixNot confirmed | Published12/23/2019 | SeverityUnknown |
CVE-2019-5098CVE-2019-5098 | Exploitation statusNot confirmed | FixNot confirmed | Published12/05/2019 | SeverityUnknown |
CVE-2019-5542CVE-2019-5542 | Exploitation statusNot confirmed | FixNot confirmed | Published11/20/2019 | SeverityUnknown |
CVE-2019-5541CVE-2019-5541 | Exploitation statusNot confirmed | FixNot confirmed | Published11/20/2019 | SeverityUnknown |
CVE-2019-5540CVE-2019-5540 | Exploitation statusNot confirmed | FixNot confirmed | Published11/20/2019 | SeverityUnknown |
CVE-2019-5536CVE-2019-5536 | Exploitation statusNot confirmed | FixNot confirmed | Published10/28/2019 | SeverityUnknown |
CVE-2019-5535CVE-2019-5535 | Exploitation statusNot confirmed | FixNot confirmed | Published10/10/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-5525CVE-2019-5525 | Exploitation statusNot confirmed | FixNot confirmed | Published06/06/2019 | SeverityUnknown |
CVE-2019-5526CVE-2019-5526 | Exploitation statusNot confirmed | FixNot confirmed | Published05/15/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-5512CVE-2019-5512 | Exploitation statusNot confirmed | FixNot confirmed | Published04/09/2019 | SeverityUnknown |
CVE-2019-5511CVE-2019-5511 | Exploitation statusNot confirmed | FixNot confirmed | Published04/09/2019 | SeverityUnknown |
CVE-2019-5515CVE-2019-5515 | Exploitation statusNot confirmed | FixNot confirmed | Published04/02/2019 | SeverityUnknown |
CVE-2019-5524CVE-2019-5524 | Exploitation statusNot confirmed | FixNot confirmed | Published04/02/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-6983CVE-2018-6983 | Exploitation statusNot confirmed | FixNot confirmed | Published11/27/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-6973CVE-2018-6973 | Exploitation statusNot confirmed | FixNot confirmed | Published08/15/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-2018-6963CVE-2018-6963 | Exploitation statusNot confirmed | FixNot confirmed | Published05/22/2018 | SeverityUnknown |
CVE-2018-5511CVE-2018-5511 | Exploitation statusPublic exploit | FixNot confirmed | Published04/13/2018 | SeverityUnknown |
CVE-2018-6957CVE-2018-6957 | Exploitation statusNot confirmed | FixNot confirmed | Published03/15/2018 | SeverityUnknown |
CVE-2017-4950CVE-2017-4950 | Exploitation statusNot confirmed | FixNot confirmed | Published01/11/2018 | SeverityUnknown |
CVE-2017-4949CVE-2017-4949 | Exploitation statusNot confirmed | FixNot confirmed | Published01/11/2018 | SeverityUnknown |
CVE-2017-4945CVE-2017-4945 | Exploitation statusNot confirmed | FixNot confirmed | Published01/05/2018 | SeverityUnknown |
CVE-2017-4948CVE-2017-4948 | Exploitation statusNot confirmed | FixNot confirmed | Published01/05/2018 | SeverityUnknown |
CVE-2017-5753CVE-2017-5753 | Exploitation statusPublic exploit | FixNot confirmed | Published01/04/2018 | SeverityMedium |
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-4939CVE-2017-4939 | Exploitation statusNot confirmed | FixNot confirmed | Published11/17/2017 | SeverityUnknown |
CVE-2017-4937CVE-2017-4937 | Exploitation statusNot confirmed | FixNot confirmed | Published11/17/2017 | SeverityUnknown |
CVE-2017-4936CVE-2017-4936 | Exploitation statusNot confirmed | FixNot confirmed | Published11/17/2017 | SeverityUnknown |
CVE-2017-4935CVE-2017-4935 | Exploitation statusNot confirmed | FixNot confirmed | Published11/17/2017 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
