Is System.Management.Automation 6.0 vulnerable?

NuGet · 2 releases from 6.0.4 to 6.0.5 · latest System.Management.Automation is 7.7.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. System.Management.Automation 6.0.5, the last 6.0 release, is affected by 1 known security advisory (1 high), including CVE-2019-1301. Upgrade to 6.1.6 or later to fix all of them.

Upgrade with:dotnet add package System.Management.Automation --version 6.1.6

Is your project on an affected System.Management.Automation?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting System.Management.Automation 6.0.5

  • HighCVE-2019-1301GHSA-62gw-3rmj-wmp213 Sept 2019

    High severity vulnerability that affects System.Management.Automation

    Affected
    >=6.2.0 <6.2.3 · >=6.0.0 <6.1.6
    Fixed in
    6.1.6, 6.2.3

Every System.Management.Automation 6.0.x release

Affected: 6.0.4 to 6.0.5. Latest System.Management.Automation: 7.7.0.

VersionKnown advisories
System.Management.Automation 6.0.5CVE-2019-1301
System.Management.Automation 6.0.4CVE-2019-1301

Which of your client projects are still on System.Management.Automation 6.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact System.Management.Automation version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other System.Management.Automation 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.