CVE-2017-4941
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 8.5.9; workstation 12.5.8 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.0 before ESXi600-201711101-SG, 5.5 ESXi550-201709101-SG), Workstation (12.x before 12.5.8), and Fusion (8.x before 8.5.9) contain a vulnerability that could allow an authenticated VNC session to cause a stack overflow via a specific set of VNC packets. Successful exploitation of this issue could result in remote code execution in a virtual machine via the authenticated VNC session. Note: In order for exploitation to be possible in ESXi, VNC must be manually enabled in a virtual machine's .vmx configuration file. In addition, ESXi must be configured to allow VNC traffic through the built-in firewall.
- weakness
- Stack overflow via authenticated VNC session
- affected
- VMware ESXi; VMware Workstation; VMware Fusion
- published ranges
- vmware fusion >= 8.0.0 < 8.5.9; vmware workstation >= 12.0.0 < 12.5.8; vmware esxi 5.5; vmware esxi 5.5-550-20170901001s; and 84 more on the CVE page
- first unaffected version, by branch
- fusion 8.5.9; workstation 12.5.8
- assigned by
- vmware
- published
- 2017-12-20
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.01828 | |
| 28 Jan 2022 | 0.00271 | |
| 4 Feb 2022 | 0.04571 | |
| 16 Sep 2022 | 0.04695 | |
| 7 Mar 2023 | 0.02897 | scoring model v2023.03.01 |
| 13 May 2023 | 0.02703 | |
| 30 Oct 2023 | 0.02564 | |
| 30 Nov 2023 | 0.02628 | |
| 14 Feb 2024 | 0.02252 | |
| 17 Dec 2024 | 0.0041 | |
| 17 Mar 2025 | 0.03561 | scoring model v2025.03.14 |
| 19 Mar 2025 | 0.05017 | |
| 29 Mar 2025 | 0.09766 | |
| 30 Mar 2025 | 0.05017 | |
| 6 Jul 2025 | 0.04776 | |
| 15 Jun 2026 | 0.03157 | scoring model v2026.06.15 |
16 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.03 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 8.5.9; workstation 12.5.8. 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-2017-4941', '2026-11-01T23:59:59.999999Z', now());