KB–CVE Mapper

A KB number names a Microsoft update. A CVE number names a vulnerability. This tool maps one to the other — in your browser, from Microsoft’s own data.

A Microsoft KB number (like KB5066128) identifies one update; a CVE number (like CVE-2025-55248) identifies one vulnerability. The link between them lives in the monthly CVRF security-update document Microsoft publishes through its Security Response Center: each vulnerability lists the updates that fix it. This mapper loads that document in your browser — download it from Microsoft first, then drag it in — and answers both directions: which CVEs a KB fixes, and which KBs fix a CVE. Try the demo: it loads a verified slice of the October 2025 release and looks up KB5066128. The companion article what KB numbers and CVEs map to walks through a real record by hand, and CVE Triage ranks CVEs by exploitation risk.

Last updated:

1. Load the data

Microsoft publishes one CVRF file per month. Load one or more months — the tool merges them into a single index.

Demo: a verified slice of the October 2025 release — 3 CVEs, 47 KBs — loaded instantly, then KB5066128 is looked up for you.

Choose or drag in one or more monthly CVRF files. The October 2025 file is about 4 MB.

No data loaded yet — load the demo data or a CVRF file to start.

Where the data comes from

1. Open api.msrc.microsoft.com/cvrf/v2.0/Updates — the public list of monthly releases (no key needed) — and pick a month, or go straight to the file for a month, for example https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2025-Oct.

2. Save the JSON file (right-click → Save as, or download it with curl). The October 2025 file is about 4 MB.

3. Drag the file into the box above, or paste its contents. The file is parsed in your browser and never uploaded.

2. Look up a KB or a CVE

Enter a KB number to see the CVEs it fixes, or a CVE number to see the KBs that fix it. The format decides the direction — no toggle needed.

🔒 Your file never leaves your browser — the CVRF document is parsed locally, and no query is sent anywhere. Microsoft’s API sends no CORS headers, so the file must be downloaded first; this page explains how.

What a CVRF document is

CVRF (Common Vulnerability Reporting Framework) is the machine-readable format Microsoft publishes each month for its security updates — one JSON document per release, listing every CVE fixed that month. The October 2025 document, for example, lists 180 Microsoft CVEs and 53 KB numbers in about 4 MB of JSON.

The KB lives in the fix, not in the CVE: each vulnerability carries a list of remediations, and each remediation is a URL — either a Microsoft Update Catalog search (catalog.update.microsoft.com/…?q=KB5066128) or a support article (support.microsoft.com/help/5066128). The KB number is read out of that URL.

The join runs through products. A vulnerability lists the ProductIDs it affects; a remediation lists the ProductIDs its KB applies to. Where the two sets overlap, that KB fixes that CVE for that product. One CVE usually needs many KBs — one per product and version — and one cumulative KB can fix a hundred or more CVEs. Both directions are real, and both are long by design.

What this mapper does — and what it does not

It builds the index locally and answers both directions. Load one or more monthly CVRF files, and the tool joins remediations to vulnerabilities through their shared ProductIDs, then shows each result with its title, MSRC severity, release date, CVSS score and vector, and affected products. Severity is the highest MSRC rating across the CVE’s products; the CVSS shown is the highest base score in the document.

It does not fetch live from Microsoft — the MSRC API sends no CORS headers, so a browser page cannot read it directly, and there is no per-KB or per-CVE endpoint. It knows nothing about KBs outside the months you loaded, it does not install or verify updates, and it does not rank exploitability — a CVSS 9.8 that nobody exploits matters less than a CVSS 7.8 that is. For that ranking, use CVE Triage.

Be honest with yourself before you trust a mapping

A mapping is only as fresh as the file you loaded. A KB from November will not appear in the October file, and a CVE fixed out-of-band will not appear in any monthly file. If a lookup comes back empty, the first question is always "which months did I load?" — not "does this KB exist?"

A long KB list for one CVE is normal, not a bug. CVE-2025-55248, a .NET information-disclosure flaw, is fixed by 33 KBs — one for each .NET Framework version on each Windows version. Pick the KB that matches your product, not the first one in the list.

Key facts

KB numberA Microsoft Knowledge Base number (KB5066128) identifies one update package — a cumulative update, a .NET update, or an out-of-band fix.
CVE numberA CVE number (CVE-2025-55248) identifies one publicly known vulnerability. One CVE is usually fixed by many KBs.
CVRF documentThe monthly JSON file Microsoft publishes per security release, listing every CVE, its remediations (with KB URLs), severity, CVSS scores and affected products.
Data sourceMicrosoft Security Response Center — Update Guide, via the public CVRF API (no key required).
Download the datahttps://api.msrc.microsoft.com/cvrf/v3.0/cvrf/YYYY-Mon — for example …/cvrf/2025-Oct. The full month list is at api.msrc.microsoft.com/cvrf/v2.0/Updates.
Severity scaleMSRC rates each CVE Critical, Important, Moderate or Low. CVSS is a separate 0–10 formula: 9.0+ Critical, 7.0–8.9 High, 4.0–6.9 Medium, 0.1–3.9 Low.

Frequently asked questions

Why do I have to download the file first instead of the tool fetching it?

Because Microsoft’s API does not send CORS headers. A page on sysosx.com cannot read api.msrc.microsoft.com directly — the browser blocks the response. Downloading the monthly JSON once and dragging it in is the honest workaround, and it has a side benefit: the file is parsed locally, so nothing about your patching ever leaves your machine.

I looked up a KB and got nothing. Is the KB fake?

Not necessarily. The likeliest cause is that the KB belongs to a month you have not loaded — a November KB will not be in the October file. Load the month the KB was released in (the Update Catalog entry for the KB says which) and try again. If it is still empty after loading the right month, the KB may be a non-security update, which CVRF does not cover.

One CVE lists 33 KBs. Which one do I install?

The one that matches your product. Each KB in the list fixes the same CVE on a different product or version — KB5066128 is the .NET Framework update for some Windows versions, while the other 32 cover other .NET versions and Windows editions. Open the KB on support.microsoft.com and check the "Applies to" list against your machines.