Vulnerability remediation · .NET

.NET Remediation Plan

Load the vulnerability findings export and the .NET App Dependencies sensor export. The page matches each finding to what the sensor found on that endpoint and says what to do: patch, remove, update, or hand to the app owner.

.NET 8, .NET 9 and PowerShell 7.4 end of supportNov 10, 2026
Your data

Files are read in your browser only. Nothing is uploaded or saved; reloading the page goes back to the data saved with it.

Drop one or both CSV exports here, or The page tells the two files apart by their columns. Load just one to replace only that one.
What the data decides

Runtime decisions backed by the sensor

For endpoints that answered the sensor question. .NET Framework rows are in the full plan below.

EndpointsComponentWhat the sensor showedAction
Full plan

Every endpoint and component

Priority 1 = KEV finding, 2 = CVSS 9 or higher, 3 = CVSS 7 or higher, 4 = lower. Open a row to see why and what the sensor found.

Search
Not in the vulnerability scan

.NET copies the scan does not report

Found only by the sensor: runtimes that products carry inside their own folders, and shared runtimes that are out of support but missing from the findings. Patching the shared .NET runtime never reaches the first kind.

Missing data

Run the sensor on these endpoints

They have .NET runtime findings but no sensor result, so it is unknown whether anything uses the runtime.

EndpointOSRuntimes in findingsKEVMax CVSSFindings
Dates

Support deadlines that drive the plan

How rows are decided

Rules and what was left out