Powershell Core vulnerabilitiesRanked by how likely they are to be used.
Powershell Core is made by Microsoft. We track 18 published vulnerabilities in it, across 17 versions. None of them is on the list of flaws known to be exploited today. If you run Powershell Core, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Powershell Core vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Powershell Core's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Powershell Core 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.
- 30%CVE-2021-26701High
.NET Core Remote Code Execution Vulnerability
- 23%CVE-2018-8256High
A remote code execution vulnerability exists when PowerShell improperly handles specially crafted files, aka "Microsoft PowerShell Remote Code Execution Vulnerability." This affects Windows RT 8.1, PowerShell Core...
- 15%CVE-2018-8292High
An information disclosure vulnerability exists in .NET Core when authentication information is inadvertently exposed in a redirect, aka ".NET Core Information Disclosure Vulnerability." This affects .NET Core 2.1,...
- 9.1%CVE-2018-0875High
.NET Core 1.0, .NET Core 1.1, NET Core 2.0 and PowerShell Core 6.0.0 allow a denial of Service vulnerability due to how specially crafted requests are handled, aka ".NET Core Denial of Service Vulnerability".
- 8.9%CVE-2018-0764High
Microsoft .NET Framework 1.1, 2.0, 3.0, 3.5, 3.5.1, 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 5.7 and .NET Core 1.0.
- 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.3%CVE-2019-1301High
A denial of service vulnerability exists when .NET Core improperly handles web requests, aka '.NET Core Denial of Service Vulnerability'.
- 4.5%CVE-2019-0657Medium
A vulnerability exists in certain .Net Framework API's and Visual Studio in the way they parse URL's, aka '.NET Framework and Visual Studio Spoofing Vulnerability'.
- 3.9%CVE-2021-26423High
.NET Core and Visual Studio Denial of Service Vulnerability
- 3.7%CVE-2018-0786High
Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, .NET Core 1.0 and 2.0, and PowerShell Core 6.0.0 allow a security feature bypass vulnerability due to the way certificates...
Running Powershell Core? 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
.NET Core Remote Code Execution Vulnerability
- Matched to
- Powershell Core 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 18 published vulnerabilities listed under the name Powershell Core, across 17 versions.
None of Powershell Core's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Powershell Core. 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.