CVE-2018-8256 in the critical feed json
A remote code execution vulnerability exists when PowerShell improperly handles specially crafted files, aka "Microsoft PowerShell Remote C…
published 2018-11-14 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-19922
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 22.6%
- EPSS 22.6% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
A remote code execution vulnerability exists when PowerShell improperly handles specially crafted files, aka "Microsoft PowerShell Remote Code Execution Vulnerability." This affects Windows RT 8.1, PowerShell Core 6.0, Microsoft.PowerShell.Archive 1.2.2.0, Windows Server 2016, Windows Server 2012, Windows Server 2008 R2, Windows Server 2019, Windows 7, Windows Server 2012 R2, PowerShell Core 6.1, Windows 10 Servers, Windows 10, Windows 8.1.
Patch / fix
Exploit prediction
22.64% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Windows 7
- Microsoft Microsoft.PowerShell.Archive
- Microsoft Windows 10 Servers
- Microsoft Windows Server 2012 R2
- Microsoft Windows RT 8.1
- Microsoft Windows Server 2008 R2
- Microsoft Windows Server 2012
- Microsoft PowerShell Core
- Microsoft Windows Server 2016
- Microsoft Windows 8.1
- Microsoft Windows 10
- Microsoft Windows Server 2019
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-8256
patch, vendor-advisory
-
securitytracker.com
/id/1042108
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/105781
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-8256
- NVD CVE-2018-8256
Fencer Vulns 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.