winsight indexes Microsoft's monthly Security Update Guide (MSRC CVRF) for every Windows CVE, resolves the binary each one actually patched, and gives you a direct download of the unpatched and patched build — so you can start diffing in two clicks instead of an afternoon of digging.

1. Search or filter down to a CVE — try a binary name like clfs.sys, a component, or a KB number.
2. Open the row and expand Patch-diff.
3. Download Unpatched and Patched, then diff them in IDA, Ghidra, or BinDiff — symbols resolve automatically from the same Microsoft symbol server.
4. Click a binary's name to open its full history: every CVE that ever touched it, and any two builds you want to compare — not just one CVE's pair.

CVSS

Severity score, 0–10, from the MSRC advisory.

EPSS

Estimated probability a CVE is exploited in the wild within 30 days. From FIRST.org, updated daily.

CISA KEV

CISA's Known Exploited Vulnerabilities catalog. If a CVE is listed, exploitation has been confirmed, not just predicted.

Exploitability Assessment

Microsoft's own likelihood label — Exploitation Detected, More/Less Likely, or Unlikely.

Unpatched / Patched

The build immediately before, and the build including, the fixing update — resolved from Winbindex's build index.

No direct link

A handful of builds (notably win32k.sys) share a symbol-server identifier with other builds of the same file, so Microsoft's server can only serve one of them. Use the Winbindex link instead.

How often does this refresh?

Weekly, around Patch Tuesday, via a GitHub Action that re-pulls the MSRC feed.

Is this affiliated with Microsoft?

No — independent, unofficial, best-effort.

Where does the data come from?

MSRC's Security Update Guide (CVRF v3), Winbindex, FIRST's EPSS, and the CISA KEV catalog.

/ focus search · Esc close panel or dialog