System.Management.Automation vulnerabilities
Runtime for hosting PowerShell
- Registry
- NuGet
- Latest
- 7.7.0
- License
- MIT
2 known advisories
The latest version, 7.7.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
dotnet add package System.Management.Automation --version 7.7.0Is your project on an affected System.Management.Automation?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for System.Management.Automation
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
System.Management.Automation subject to bypass via script debugging
- Affected
- >=6.2.0 <6.2.2 · >=6.1.0 <6.1.5
- Fixed in
- 6.1.5, 6.2.2
Is your System.Management.Automation version vulnerable?
- System.Management.Automation 7.7No known advisories in 7.7.0
- System.Management.Automation 7.6No known advisories in 7.6.10
- System.Management.Automation 7.5No known advisories in 7.5.13
- System.Management.Automation 7.4No known advisories in 7.4.22
- System.Management.Automation 7.3No known advisories in 7.3.12
- System.Management.Automation 7.2No known advisories in 7.2.24
- System.Management.Automation 6.2No known advisories in 6.2.7
- System.Management.Automation 6.1No known advisories in 6.1.6
- System.Management.Automation 6.01 advisory in 6.0.5
Which of your client projects still run an old System.Management.Automation?
NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other NuGet packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.