CVE-2018-8440: Microsoft Windows Privilege Escalation
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-28.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 19%
- higher than 97.3% of all CVEs
- Added to CISA KEV
- 2022-03-28
- US federal due date 2022-04-18
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2018-8440 explained
CVE-2018-8440 is an elevation of privilege vulnerability in Microsoft Windows. It stems from improper handling of calls to Advanced Local Procedure Call (ALPC). CISA lists it as known to be exploited, including in ransomware campaigns, so unpatched Windows systems face real risk.
Impact
An attacker who can already run code on a system with low privileges can gain elevated rights without any user interaction. CISA rates the technical impact as total, meaning full control of the affected system, with high impact on confidentiality, integrity and availability. Exploitation is local and not automatable at scale, so it is typically chained after an initial foothold. Attackers are known to use it, including in ransomware.
Who is affected
The record lists Windows 7 SP1, Windows 8.1, Windows RT 8.1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012 and 2012 R2, Windows Server 2016, and Windows 10 (including Version 1607 for x64-based Systems, Version 1703 for x64-based Systems, Version 1709 for x64-based Systems, plus further items). Windows 10 Servers version 1709 (Server Core Installation) and version 1803 (Server Core Installation) are also affected. The CVE record names no fixed version.
Written with AI from the data on this page and checked against it automatically.
Official description
An elevation of privilege vulnerability exists when Windows improperly handles calls to Advanced Local Procedure Call (ALPC), aka "Windows ALPC Elevation of Privilege 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-04-18 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security update for CVE-2018-8440 to all affected Windows systems, following the vendor advisory.
- Prioritize servers and workstations where untrusted or many low-privileged users can run code.
- Replace or upgrade Windows versions that no longer receive security updates.
- Check systems for signs of compromise, especially unexpected privilege changes or ransomware activity.
- Limit local logon rights and restrict running untrusted code to reduce the chance of an initial foothold.
The CVE record names no fixed version for the listed products. Follow the Microsoft advisory to identify and install the applicable security update for each Windows version. CISA's required action is to apply updates per vendor instructions. Until updates are installed, restrict who can log on locally and run code, and monitor for signs of compromise.
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
Questions about CVE-2018-8440
- Can this be exploited remotely?
- No. The attack vector is local. An attacker needs low-privileged access to the system first, then can use this flaw to gain elevated privileges without user interaction.
- Is this vulnerability actively exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-28 and notes known use in ransomware campaigns. The US federal due date was 2022-04-18.
- What does CISA require?
- CISA's required action is to apply updates per vendor instructions. Use the Microsoft advisory to find the correct update for each affected Windows version.
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.