MSRC security updates
Microsoft vulnerability review
Loading MSRC feed coverage…
Counts represent CVE records in monthly MSRC feeds, including Linux and third-party components. They are not counts of newly disclosed vulnerabilities or patches to install.
How dates and counts work
First recorded means the earliest valid revision date in the selected MSRC source. Timing compares that date with the second Tuesday of the source month, using calendar dates as supplied by MSRC. It does not establish original disclosure, fix availability or an official out-of-band release. Missing dates stay Unknown. Fix dates appear on individual remediation references where supplied.
All releases deduplicates CVEs using the most recently revised source record; monthly appearances can therefore exceed the unique total. Each view keeps its own filters.
Advisories
Advisories are shown separately and excluded from CVE totals. Review their source guidance for required actions.
Prioritised by MSRC exploitation and disclosure indicators, then severity and CVSS. MSRC indicators describe the overall CVE; they do not measure your environment’s exposure.
Updates by product
References associated with the current results or shortlist, grouped by product, update and build. Confirm applicability and prerequisites in the source; an associated CVE does not prove this update alone completes remediation.
Updated dates come from each CVE's latest MSRC revision.
Loading vulnerabilities…
| Shortlist | MSRC indicators | Details |
|---|
Public researcher attribution for every CVE in the selected month. Missing severity, impact, or credit is shown explicitly.
Explore attribution breakdown
Impact
Published credit
—CVEs shown
Charts and summaries count the visible CVEs. Multiple impacts can overlap. Product-filtered severity and impacts use matching products. Credit labels describe acknowledgement text, not employment, discovery method or a submission channel.
| CVE / title | Severity | Impact | Reporting | Products | Published credit | Details |
|---|