Microsoft KB–CVE Mapping Explained
Last updated:
A Microsoft KB number and a CVE number look like the same kind of thing — a code with a year and a serial — but they answer different questions. A KB number, like KB5066128, identifies one update package: a file you install. A CVE number, like CVE-2025-55248, identifies one vulnerability: a flaw somebody found. The mapping between them — which update fixes which flaw — is not printed on either one. It lives in a third place: the monthly CVRF security-update document Microsoft publishes, where each vulnerability lists the updates that fix it. This article reads one real record by hand, explains why a single CVE can need 33 different KBs, and shows where the mapping breaks down.
A KB number and a CVE number answer different questions
A KB number comes from the Microsoft Knowledge Base. It names a deliverable: a cumulative update, a .NET update, an out-of-band fix. When Windows Update offers you KB5066128, it is offering you a package — a set of files, a restart, a line in your update history. The number tells you what to install, and the support article behind it tells you what changed. It says nothing, on its own, about which vulnerabilities the package addresses.
A CVE number comes from the other direction. It names a flaw, not a fix: a weakness in a product, given a public ID so that everyone — Microsoft, NIST, your scanner, your vendor — can talk about the same bug without confusion. CVE-2025-55248 is an information-disclosure flaw in .NET, .NET Framework and Visual Studio. The CVE says what is wrong and how bad it is; it does not say which update to install, because the answer depends on which product and version you run. One flaw, many updates — and that is where the mapping earns its keep.
Where the mapping lives: the monthly CVRF document
Microsoft publishes the mapping once a month, as a machine-readable JSON document in the Common Vulnerability Reporting Framework (CVRF) format. One document per security release, available from the public MSRC API with no key: the Updates endpoint lists the months, and each month has its own file — for example, https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2025-Oct. The October 2025 document is about 4 MB and lists 180 Microsoft CVEs and 53 KB numbers. It is the authoritative source, and everything in this article — and in the KB–CVE Mapper tool — comes from it.
The mapping itself is a join, not a lookup table. A vulnerability record carries two lists that matter: ProductStatuses, the ProductIDs the flaw affects, and Remediations, the fixes — 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. Where the remediation’s ProductIDs overlap the vulnerability’s ProductIDs, that KB fixes that CVE for that product. There is no per-KB or per-CVE endpoint in the API — the document is the database, and the join is the query.
Reading a real record: KB5066128 and CVE-2025-55248
Take the cleanest pair in the October 2025 release. CVE-2025-55248 is titled ".NET, .NET Framework, and Visual Studio Information Disclosure Vulnerability": inadequate encryption strength in .NET, rated Important by Microsoft, with a CVSS 3.1 base score of 4.8 and the vector CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C. Its remediation list contains two entries carrying KB5066128 — a catalog search URL and a support article URL — alongside entries for 32 other KBs. Ask the document "what does KB5066128 fix?" and the answer is exactly one CVE: this one.
Ask the reverse question — "which KBs fix CVE-2025-55248?" — and the answer is 33. That asymmetry is the whole story of this mapping: it is one-to-many in one direction and many-to-one in the other, and both directions are correct at the same time. The record itself shows you why: the vulnerability affects 78 product entries (every supported .NET Framework 4.8 install, from Windows Server 2008 R2 to Windows 11), and each product line gets its own KB. KB5066128 is the .NET update for some of those Windows versions; the other 32 cover the rest. The code sample below is the record itself, trimmed to the parts that carry the mapping.
Why one CVE needs 33 KBs — and one KB fixes 100 CVEs
The 33 KBs for CVE-2025-55248 are not 33 different fixes for the same bug. They are the same fix, packaged 33 times: once per .NET version, once per Windows version, once per architecture where the packaging differs. Microsoft ships updates per product line, not per vulnerability, so a flaw that touches a widely shipped component — .NET Framework 4.8 runs on everything from Server 2008 R2 to Windows 11 — necessarily fans out into dozens of KBs. Pick the KB that matches your product, not the first one in the list: the support article for each KB carries an "Applies to" list, and that list is the last step of the mapping.
The reverse direction fans out even further. A cumulative update is a bundle: one KB that rolls up every fix for its product that month. KB5065426, the October 2025 cumulative update for one Windows line, fixes 134 CVEs in that month’s document. That is not an error in the data — it is what "cumulative" means. So a KB→CVE lookup that returns a hundred rows is telling the truth, and a CVE→KB lookup that returns 33 rows is telling the truth too. If either direction ever returns exactly one row, that is the exception worth noticing — like KB5066128, whose single CVE makes it the cleanest demo of the mapping there is.
Severity is not CVSS: two scales that disagree on purpose
Every CVE in the CVRF document carries two different judgements, and they measure different things. The MSRC severity — Critical, Important, Moderate or Low — is Microsoft’s own rating: how bad is this flaw in our products, for our customers, in practice? The CVSS base score — 0 to 10, with its vector string — is a formula: attack vector, complexity, privileges, user interaction, impact. CVE-2025-55248 is Important with a CVSS of 4.8 (Medium); CVE-2025-24052, a Windows modem-driver privilege escalation, is also Important but scores 7.8 (High). Same vendor word, very different formula numbers.
The two scales can even disagree with themselves inside one record. CVE-2025-2884, an out-of-bounds read in the TPM 2.0 reference implementation, is rated Critical on some products and Important on others — the threat entries are per product, so the record’s severity is the highest across its products. The mapper reports that highest value, and the highest CVSS base score the same way. Neither scale ranks exploitability: a CVSS 9.8 nobody exploits matters less than a CVSS 7.8 that is being exploited right now. That ranking is a different job — it is what the CVE Triage tool does with CISA’s Known Exploited Vulnerabilities catalog and EPSS scores — and confusing the two is the most common mistake in patch prioritisation.
What the mapper does — and what it cannot do
The KB–CVE Mapper loads the monthly CVRF files in your browser and answers both directions of the question, with each result’s title, severity, release date, CVSS score and affected products, plus a CSV export of the table. It never uploads anything: the file is parsed locally, and the demo runs on a verified three-CVE slice of the October 2025 release so you can see a real answer — KB5066128 → CVE-2025-55248 — with one click. Load more months and the index merges them; a later month’s revision of a record replaces the earlier one.
What it cannot do is fetch live. The MSRC API sends no CORS headers, so a page on sysosx.com cannot read api.msrc.microsoft.com directly — the browser blocks the response — and there is no per-KB or per-CVE endpoint to call. That is why the tool asks you to download the monthly JSON first: it is the honest workaround, and it has a side benefit your patching history never leaves your machine. It also cannot know about KBs outside the months you loaded, and it cannot tell you whether a KB is installed — that is what Windows Update history and your patch-management tool are for. A mapping is a map, not the territory: check the month, check the product, then install.
Try it yourself: one CVE record, trimmed to the parts that carry the mapping
{
"CVE": "CVE-2025-55248",
"Title": {
"Value": ".NET, .NET Framework, and Visual Studio
Information Disclosure Vulnerability"
},
"Threats": [
{ "Type": 3, "Description": { "Value": "Important" } }
],
"CVSSScoreSets": [
{
"BaseScore": 4.8,
"Vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C"
}
],
"Remediations": [
{
"Type": 2,
"URL": "https://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5066128"
},
{
"Type": 3,
"URL": "https://support.microsoft.com/help/5066128"
}
]
}