CVE-2018-8174: Microsoft Windows VBScript Engine Out-of-Bounds Write
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-02-15.
- CVSS v3.1 (CISA ADP)
- 7.5
- high
- EPSS (exploit probability, 30 days)
- 88%
- higher than 99.7% of all CVEs
- Added to CISA KEV
- 2022-02-15
- US federal due date 2022-08-15
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2018-8174 explained
CVE-2018-8174 is a remote code execution vulnerability in the Windows VBScript engine, caused by the way the engine handles objects in memory (an out-of-bounds write). It affects many Windows client and server releases. CISA lists it as known to be exploited, including in ransomware campaigns, which makes patching a priority.
Impact
An attacker who succeeds can run code on the affected system. The result is a full loss of confidentiality, integrity and availability, and CISA rates the technical impact as total. The attack works over the network and needs no privileges. It does require user interaction, and attack complexity is high. CISA does not consider it automatable. Attackers are known to exploit it, including for ransomware.
Who is affected
The CVE record lists Windows 7 SP1, Windows 8.1, Windows RT 8.1 and Windows 10. Listed Windows 10 releases include versions 1607, 1703 and 1709, with more items on the page. It also lists Windows Server 2008 SP2 and Server 2008 R2 SP1, Server 2012, Server 2012 R2 and Server 2016 (Server Core installations listed), and Windows 10 Servers versions 1709 and 1803 (Server Core). The record names no fixed version for any product.
Written with AI from the data on this page and checked against it automatically.
Official description
A remote code execution vulnerability exists in the way that the VBScript engine handles objects in memory, aka "Windows VBScript Engine Remote Code Execution Vulnerability." This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2008, Windows Server 2012, Windows 8.1, Windows Server 2016, Windows Server 2008 R2, Windows 10, Windows 10 Servers.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 7AffectedFixed in
- 32-bit Systems Service Pack 1
- x64-based Systems Service Pack 1
not stated - Microsoft Windows Server 2012 R2AffectedFixed in
- (Server Core installation)
not statedVersion statement as published by the CNA (free text).
- Microsoft Windows RT 8.1AffectedFixed in
- Windows RT 8.1
not stated - Microsoft Windows Server 2008AffectedFixed in
- Itanium-Based Systems Service Pack 2
- 32-bit Systems Service Pack 2
- x64-based Systems Service Pack 2
- 32-bit Systems Service Pack 2 (Server Core installation)
- x64-based Systems Service Pack 2 (Server Core installation)
not stated - Microsoft Windows Server 2012AffectedFixed in
- (Server Core installation)
not statedVersion statement as published by the CNA (free text).
- Microsoft Windows 8.1AffectedFixed in
- 32-bit systems
- x64-based systems
not stated - Microsoft Windows Server 2016AffectedFixed in
- (Server Core installation)
not statedVersion statement as published by the CNA (free text).
- Microsoft Windows Server 2008 R2AffectedFixed in
- Itanium-Based Systems Service Pack 1
- x64-based Systems Service Pack 1
- x64-based Systems Service Pack 1 (Server Core installation)
not stated - Microsoft Windows 10AffectedFixed in
- 32-bit Systems
- x64-based 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 x64-based Systems
- Version 1803 for 32-bit Systems
- Version 1803 for x64-based Systems
not stated - Microsoft Windows 10 ServersAffectedFixed in
- version 1709 (Server Core Installation)
- version 1803 (Server Core Installation)
not statedVersion statement as published by the CNA (free text).
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 7 |
| not stated |
| Microsoft Windows Server 2012 R2Version statement as published by the CNA (free text). |
| not stated |
| Microsoft Windows RT 8.1 |
| not stated |
| Microsoft Windows Server 2008 |
| not stated |
| Microsoft Windows Server 2012Version statement as published by the CNA (free text). |
| not stated |
| Microsoft Windows 8.1 |
| not stated |
| Microsoft Windows Server 2016Version statement as published by the CNA (free text). |
| not stated |
| Microsoft Windows Server 2008 R2 |
| not stated |
| Microsoft Windows 10 |
| not stated |
| Microsoft Windows 10 ServersVersion statement as published by the CNA (free text). |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
- CISA's deadline for US federal agencies: 2022-08-15 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply Microsoft's security updates for CVE-2018-8174 to all affected Windows systems, following the vendor advisory.
- Prioritize patching, because CISA lists the vulnerability as known exploited with ransomware use.
- Verify update installation across client and server systems, including Server Core installations.
- Replace or upgrade Windows releases that no longer receive security updates from Microsoft.
- Check systems for signs of compromise, especially any that stayed unpatched for a long time.
The CVE record names no fixed version. This does not mean no fix exists. CISA's required action is to apply updates per vendor instructions. Use Microsoft's advisory to identify the correct update for each affected Windows release and install it.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-787 Out-of-bounds Write
Questions about CVE-2018-8174
- Is CVE-2018-8174 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-02-15 and notes known ransomware use. The US federal due date for remediation was 2022-08-15.
- Can it be exploited without user action?
- No. The CVSS assessment says user interaction is required and attack complexity is high. No privileges are needed, though, and a successful attack gives total control of the affected component.
- Which version fixes the issue?
- The CVE record does not name fixed versions. Follow Microsoft's advisory and apply the security updates it lists for your Windows release, as CISA requires.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.