Is PowerShell 6.2 vulnerable?
NuGet · 6 releases from 6.2.2 to 6.2.7 · latest PowerShell is 7.7.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. PowerShell 6.2.7, the last 6.2 release, is affected by 1 known security advisory (1 high). Upgrade to 7.0.0 or later to fix all of them.
dotnet add package PowerShell --version 7.0.0Is your project on an affected PowerShell?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting PowerShell 6.2.7
PowerShell is subject to remote code execution vulnerability
- Affected
- <7.0.0
- Fixed in
- 7.0.0
Every PowerShell 6.2.x release
Affected: 6.2.2 to 6.2.7. Latest PowerShell: 7.7.0.
| Version | Known advisories |
|---|---|
| PowerShell 6.2.7 | GHSA-jcmq-5rrv-j2g4 |
| PowerShell 6.2.6 | GHSA-jcmq-5rrv-j2g4 |
| PowerShell 6.2.5 | GHSA-jcmq-5rrv-j2g4 |
| PowerShell 6.2.4 | GHSA-jcmq-5rrv-j2g4 |
| PowerShell 6.2.3 | GHSA-jcmq-5rrv-j2g4 |
| PowerShell 6.2.2 | GHSA-jcmq-5rrv-j2g4 |
Which of your client projects are still on PowerShell 6.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact PowerShell version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other PowerShell versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.