PowerShell Elevation of Privilege Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.4.13, 7.5.4, 10.0.10240.21161, 10.0.14393.8519, 10.0.17763.7919, and 12 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Improper access control in Microsoft PowerShell allows an authorized attacker to elevate privileges locally.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Microsoft PowerShell 7.4
From 7.4.0 · fixed in 7.4.13
- Microsoft PowerShell 7.5
From 7.5.0 · fixed in 7.5.4
- Microsoft Windows 10 Version 1507
From 10.0.10240.0 · fixed in 10.0.10240.21161
- Microsoft Windows 10 Version 1607
From 10.0.14393.0 · fixed in 10.0.14393.8519
- Microsoft Windows 10 Version 1809
From 10.0.17763.0 · fixed in 10.0.17763.7919
- Microsoft Windows 10 Version 21H2
From 10.0.19044.0 · fixed in 10.0.19044.6456
- Microsoft Windows 10 Version 22H2
From 10.0.19045.0 · fixed in 10.0.19045.6456
- Microsoft Windows 11 version 22H2
From 10.0.22621.0 · fixed in 10.0.22621.6060
- Microsoft Windows 11 version 22H3
From 10.0.22631.0 · fixed in 10.0.22631.6060
- Microsoft Windows 11 Version 23H2
From 10.0.22631.0 · fixed in 10.0.22631.6060
- Microsoft Windows 11 Version 24H2
From 10.0.26100.0 · fixed in 10.0.26100.6899
- Microsoft Windows 11 Version 25H2
From 10.0.26200.0 · fixed in 10.0.26200.6899
- Microsoft Windows Server 2008 R2 Service Pack 1
From 6.1.7601.0 · fixed in 6.1.7601.27974
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
From 6.1.7601.0 · fixed in 6.1.7601.27974
- Microsoft Windows Server 2008 Service Pack 2
From 6.0.6003.0 · fixed in 6.0.6003.23571
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)
From 6.0.6003.0 · fixed in 6.0.6003.23571
- Microsoft Windows Server 2012
From 6.2.9200.0 · fixed in 6.2.9200.25722
- Microsoft Windows Server 2012 (Server Core installation)
From 6.2.9200.0 · fixed in 6.2.9200.25722
- Microsoft Windows Server 2012 R2
From 6.3.9600.0 · fixed in 6.3.9600.22824
- Microsoft Windows Server 2012 R2 (Server Core installation)
From 6.3.9600.0 · fixed in 6.3.9600.22824
- Microsoft Windows Server 2016
From 10.0.14393.0 · fixed in 10.0.14393.8519
- Microsoft Windows Server 2016 (Server Core installation)
From 10.0.14393.0 · fixed in 10.0.14393.8519
- Microsoft Windows Server 2019
From 10.0.17763.0 · fixed in 10.0.17763.7919
- Microsoft Windows Server 2019 (Server Core installation)
From 10.0.17763.0 · fixed in 10.0.17763.7919
- Microsoft Windows Server 2022
From 10.0.20348.0 · fixed in 10.0.20348.4294
- Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
From 10.0.25398.0 · fixed in 10.0.25398.1913
- Microsoft Windows Server 2025
From 10.0.26100.0 · fixed in 10.0.26100.6899
- Microsoft Windows Server 2025 (Server Core installation)
From 10.0.26100.0 · fixed in 10.0.26100.6899