CVE-2019-5521 in the critical feed json
VMware ESXi (6.7 before ESXi670-201904101-SG and 6.5 before ESXi650-201903001), Workstation (15.x before 15.0.3 and 14.x before 14.1.6) and…
published 7y ago modified 4mo ago also EUVD-2019-15096
- cvss
- 9.6
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
VMware ESXi (6.7 before ESXi670-201904101-SG and 6.5 before ESXi650-201903001), Workstation (15.x before 15.0.3 and 14.x before 14.1.6) and Fusion (11.x before 11.0.3 and 10.x before 10.1.6) contain an out-of-bounds read vulnerability in the pixel shader functionality. Successful exploitation of this issue may lead to information disclosure or may allow attackers with normal user privileges to create a denial-of-service condition on the host. Exploitation of this issue require an attacker to have access to a virtual machine with 3D graphics enabled. It is not enabled by default on ESXi and is enabled by default on Workstation and Fusion.
Patch / fix
- vmware fusion 10.1.6, 11.0.3
- vmware workstation 14.1.6, 15.0.3
Is CVE-2019-5521 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.63% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H |
| NVD | 2.0 | 5.5 | AV:N/AC:L/Au:S/C:P/I:N/A:P |
Affected products
- VMware VMware ESXi
- VMware VMware Workstation
- VMware VMware Fusion
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
vmware.com
/security/advisories/VMSA-2019-0012.html
vendor-advisory
-
talosintelligence.com
/vulnerability_reports/TALOS-2019-0757
third-party-advisory
Sources
- CVE List CVE-2019-5521
- NVD CVE-2019-5521
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.