CVE-2019-5521
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: fusion 10.1.6; fusion 11.0.3; workstation 14.1.6; workstation 15.0.3 upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
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.
- weakness
- Out of bounds read vulnerability
- affected
- VMware ESXi; VMware Workstation; VMware Fusion
- published ranges
- vmware fusion >= 10.0.0 < 10.1.6; vmware fusion >= 11.0.0 < 11.0.3; vmware workstation >= 14.0.0 < 14.1.6; vmware workstation >= 15.0.0 < 15.0.3; and 116 more on the CVE page
- first unaffected version, by branch
- fusion 10.1.6; fusion 11.0.3; workstation 14.1.6; workstation 15.0.3
- assigned by
- vmware
- published
- 2019-09-20
check us talosintelligence.com vmware.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 14 Apr 2021 | 0.00624 | |
| 6 Jan 2022 | 0.02742 | |
| 4 Feb 2022 | 0.09029 | |
| 1 Apr 2022 | 0.00885 | |
| 7 Mar 2023 | 0.00076 | scoring model v2023.03.01 |
| 8 Mar 2023 | 0.00076 | |
| 17 Dec 2024 | 0.00087 | |
| 10 Feb 2025 | 0.00114 | |
| 17 Mar 2025 | 0.00422 | scoring model v2025.03.14 |
| 29 Mar 2025 | 0.0088 | |
| 30 Mar 2025 | 0.00422 | |
| 6 Oct 2025 | 0.00408 | |
| 5 Nov 2025 | 0.0044 | |
| 25 Dec 2025 | 0.00418 | |
| 15 Jun 2026 | 0.01628 | scoring model v2026.06.15 |
15 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.02 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: fusion 10.1.6; fusion 11.0.3; workstation 14.1.6; workstation 15.0.3. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2019-5521', '2026-10-30T23:59:59.999999Z', now());