Powershell vulnerabilitiesRanked by how likely they are to be used.
Powershell is made by Microsoft. We track 21 published vulnerabilities listed under that exact name, across 270 versions. None of them is on the list of flaws known to be exploited today. Microsoft lists newer releases under their own names, such as Powershell Core, so check those pages too.
We keep watching the known-exploited list.
Is Powershell listed under other names? Yes.
Microsoft also lists Powershell under more specific names, such as Powershell Core and Powershell Editor Services. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Powershell vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Powershell's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Powershell flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 61%CVE-2022-41076High
PowerShell Remote Code Execution Vulnerability
- 20%CVE-2021-41355Medium
.NET Core and Visual Studio Information Disclosure Vulnerability
- 6.6%CVE-2020-0951Medium
<p>A security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement.
- 6.5%CVE-2020-1108High
A denial of service vulnerability exists when .NET Core or .NET Framework improperly handles web requests, aka '.NET Core & .NET Framework Denial of Service Vulnerability'.
- 5.7%CVE-2022-23267High
.NET and Visual Studio Denial of Service Vulnerability
- 3.2%CVE-2020-8927Medium
A buffer overflow exists in the Brotli library versions prior to 1.0.8 where an attacker controlling the input length of a "one-shot" decompression request to a script can trigger a crash, which happens when copying...
- 3.1%CVE-2024-21392High
.NET and Visual Studio Denial of Service Vulnerability
- 3.0%CVE-2024-26190High
Microsoft QUIC Denial of Service Vulnerability
- 2.8%CVE-2024-0057Critical
NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability
- 2.8%CVE-2023-21538High
.NET Denial of Service Vulnerability
Running Powershell? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
PowerShell Remote Code Execution Vulnerability
- Matched to
- Powershell on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 21 published vulnerabilities listed under the name Powershell, across 270 versions.
None of Powershell's vulnerabilities is on the list of flaws known to be exploited today.
Microsoft also lists Powershell under more specific names, such as Powershell Core and Powershell Editor Services. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Powershell. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.