CVE-2018-8476 in the critical feed json
A remote code execution vulnerability exists in the way that Windows Deployment Services TFTP Server handles objects in memory, aka "Window…
published 2018-11-14 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-20106
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 64.8%
- EPSS 64.8% chance of exploitation in 30 days, percentile 99.2%
- public exploits
- 0
- none known
Summary
A remote code execution vulnerability exists in the way that Windows Deployment Services TFTP Server handles objects in memory, aka "Windows Deployment Services TFTP Server Remote Code Execution Vulnerability." This affects Windows Server 2012 R2, Windows Server 2008, Windows Server 2012, Windows Server 2019, Windows Server 2016, Windows Server 2008 R2, Windows 10 Servers.
Patch / fix
Exploit prediction
64.83% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Windows Server 2012 R2
- Microsoft Windows Server 2008
- Microsoft Windows Server 2012
- Microsoft Windows Server 2019
- Microsoft Windows Server 2016
- Microsoft Windows Server 2008 R2
- Microsoft Windows 10 Servers
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-8476
patch, vendor-advisory
-
securitytracker.com
/id/1042109
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/105774
vdb-entry, third-party-advisory
- research.checkpoint.com /2019/pxe-dust-finding-a-vulnerability-in-windows-servers-deployment-services/
Sources
- CVE List CVE-2018-8476
- NVD CVE-2018-8476
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.