PoC Monitor
← All CVEs
CVE-2025-54100published 9 Dec 2025 17:56 UTCData: JSON · API

Microsoft Windows 10

PowerShell Remote Code Execution Vulnerability

Improper neutralization of special elements used in a command ('command injection') in Windows PowerShell allows an unauthorized attacker to execute code locally.

First public PoC 3.5 daysafter publication · 13 Dec 2025
Public PoCs22 on GitHub
CVSS7.8high · scored by CNA · CWE-77
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Microsoft Windows 10 Version 1607
  • >= 10.0.14393.0, < 10.0.14393.8688

Fixed in 10.0.14393.8688

Microsoft Windows 10 Version 1809
  • >= 10.0.17763.0, < 10.0.17763.8146

Fixed in 10.0.17763.8146

Microsoft Windows 10 Version 21H2
  • >= 10.0.19044.0, < 10.0.19044.6691

Fixed in 10.0.19044.6691

Microsoft Windows 10 Version 22H2
  • >= 10.0.19045.0, < 10.0.19045.6691

Fixed in 10.0.19045.6691

Microsoft Windows 11 version 22H3
  • >= 10.0.22631.0, < 10.0.22631.6345

Fixed in 10.0.22631.6345

Microsoft Windows 11 Version 23H2
  • >= 10.0.22631.0, < 10.0.22631.6345

Fixed in 10.0.22631.6345

Microsoft Windows 11 Version 24H2
  • >= 10.0.26100.0, < 10.0.26100.7462

Fixed in 10.0.26100.7462

Microsoft Windows 11 Version 25H2
  • >= 10.0.26200.0, < 10.0.26200.7462

Fixed in 10.0.26200.7462

Microsoft Windows Server 2008 R2 Service Pack 1
  • >= 6.1.7601.0, < 6.1.7601.28064

Fixed in 6.1.7601.28064

Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
  • >= 6.1.7601.0, < 6.1.7601.28064

Fixed in 6.1.7601.28064

Microsoft Windows Server 2008 Service Pack 2
  • >= 6.0.6003.0, < 6.0.6003.23666

Fixed in 6.0.6003.23666

Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)
  • >= 6.0.6003.0, < 6.0.6003.23666

Fixed in 6.0.6003.23666

Microsoft Windows Server 2012
  • >= 6.2.9200.0, < 6.2.9200.25815

Fixed in 6.2.9200.25815

Microsoft Windows Server 2012 (Server Core installation)
  • >= 6.2.9200.0, < 6.2.9200.25815

Fixed in 6.2.9200.25815

Microsoft Windows Server 2012 R2
  • >= 6.3.9600.0, < 6.3.9600.22920

Fixed in 6.3.9600.22920

Microsoft Windows Server 2012 R2 (Server Core installation)
  • >= 6.3.9600.0, < 6.3.9600.22920

Fixed in 6.3.9600.22920

Microsoft Windows Server 2016
  • >= 10.0.14393.0, < 10.0.14393.8688

Fixed in 10.0.14393.8688

Microsoft Windows Server 2016 (Server Core installation)
  • >= 10.0.14393.0, < 10.0.14393.8688

Fixed in 10.0.14393.8688

Microsoft Windows Server 2019
  • >= 10.0.17763.0, < 10.0.17763.8146

Fixed in 10.0.17763.8146

Microsoft Windows Server 2019 (Server Core installation)
  • >= 10.0.17763.0, < 10.0.17763.8146

Fixed in 10.0.17763.8146

Microsoft Windows Server 2022
  • >= 10.0.20348.0, < 10.0.20348.4529

Fixed in 10.0.20348.4529

Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • >= 10.0.25398.0, < 10.0.25398.2025

Fixed in 10.0.25398.2025

Microsoft Windows Server 2025
  • >= 10.0.26100.0, < 10.0.26100.7462

Fixed in 10.0.26100.7462

Microsoft Windows Server 2025 (Server Core installation)
  • >= 10.0.26100.0, < 10.0.26100.7462

Fixed in 10.0.26100.7462

Mitigation

Upgrade Windows 10 Version 1607 to 10.0.14393.8688 or later.

Upgrade Windows 10 Version 1809 to 10.0.17763.8146 or later.

Upgrade Windows 10 Version 21H2 to 10.0.19044.6691 or later.

Upgrade Windows 10 Version 22H2 to 10.0.19045.6691 or later.

Upgrade Windows 11 version 22H3 to 10.0.22631.6345 or later.

Upgrade Windows 11 Version 23H2 to 10.0.22631.6345 or later.

Upgrade Windows 11 Version 24H2 to 10.0.26100.7462 or later.

Upgrade Windows 11 Version 25H2 to 10.0.26200.7462 or later.

Upgrade Windows Server 2008 R2 Service Pack 1 to 6.1.7601.28064 or later.

Upgrade Windows Server 2008 R2 Service Pack 1 (Server Core installation) to 6.1.7601.28064 or later.

Upgrade Windows Server 2008 Service Pack 2 to 6.0.6003.23666 or later.

Upgrade Windows Server 2008 Service Pack 2 (Server Core installation) to 6.0.6003.23666 or later.

Upgrade Windows Server 2012 to 6.2.9200.25815 or later.

Upgrade Windows Server 2012 (Server Core installation) to 6.2.9200.25815 or later.

Upgrade Windows Server 2012 R2 to 6.3.9600.22920 or later.

Upgrade Windows Server 2012 R2 (Server Core installation) to 6.3.9600.22920 or later.

Upgrade Windows Server 2016 to 10.0.14393.8688 or later.

Upgrade Windows Server 2016 (Server Core installation) to 10.0.14393.8688 or later.

Upgrade Windows Server 2019 to 10.0.17763.8146 or later.

Upgrade Windows Server 2019 (Server Core installation) to 10.0.17763.8146 or later.

Upgrade Windows Server 2022 to 10.0.20348.4529 or later.

Upgrade Windows Server 2022, 23H2 Edition (Server Core installation) to 10.0.25398.2025 or later.

Upgrade Windows Server 2025 to 10.0.26100.7462 or later.

Upgrade Windows Server 2025 (Server Core installation) to 10.0.26100.7462 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published9 Dec 2025 · t = 0First public PoC13 Dec 2025 · t+3.5d

First public PoC 3.5 days after publication; not in CISA KEV. First PoC: ThemeHackers/CVE-2025-54100 (created 13 Dec 2025, found by us: backfilled).

PoC repositories

Found on GitHub.

2 PoCs · 1 informational

PoCs 2
RepositoryCreatedStarsAssessment
ThemeHackers/CVE-2025-54100 13 Dec 2025 +3.5 d 31 PoC
xiaoLvChen/CVE-2025-54100 29 Dec 2025 +20 d 2 PoC
Informational 1
RepositoryCreatedStarsAssessment
osman1337-security/CVE-2025-54100 9 Dec 2025 +3 h 24 Informational · write-up
Flags · score 20
  • stars without code

Below the suspicion threshold (50); does not change the assessment.

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.