Patch tracker / CVE reference / CVE-2022-2601
CVE-2022-2601
CVE-2022-2601 is a critical severity Microsoft vulnerability with a CVSS score of 9.8. Its EPSS score puts the probability of exploitation in the next 30 days at 41%. Microsoft has shipped the fix: deploy one of the 11 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.
Critical severity Microsoft vulnerability, CVSS 9.8. Fixed by 11 Microsoft security updates.
Risk summary
Updated July 24, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2022-2601
A 2022-era grub2 bootloader buffer overflow is still on the books for Azure Linux 3.0 and CBL Mariner images, where it can undermine the boot trust chain; the age is the story, roughly four years of exposure window for anything unpatched. It carries a Critical 9.8 score and a 39 percent EPSS. Boot-chain flaws survive OS rebuilds, which makes them uncomfortable to leave open.
Do this: Update grub2 on Azure Linux and CBL Mariner nodes and verify Secure Boot revocations are applied.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2022-2601
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2022-2601
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
Exploitation and severity
Not in the CISA KEV catalog. EPSS exploit probability 41%. CVSS 9.8 (Critical).
This CVE is among the top half of tracked Microsoft CVEs by EPSS exploit probability.
Official patch(es) for CVE-2022-2601
Elevated priority: high severity or a meaningful exploitation probability, sooner if an affected product is internet-facing. In Intune or Defender, confirm whether the fixing updates KB5041592, KB5055518, KB5055519, KB5055521, KB5055523, KB5055526, KB5055527, KB5055528, KB5055547, KB5055557, KB5055581 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.
Apply the Microsoft security updates below to fix CVE-2022-2601. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.
Affected products
Common questions about CVE-2022-2601
Is CVE-2022-2601 actively exploited?
It is not currently listed in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score puts the probability of exploitation in the next 30 days at 41%.
What patch fixes CVE-2022-2601?
Microsoft fixed CVE-2022-2601 in KB5041592, KB5055518, KB5055519, KB5055521, KB5055523, KB5055526, KB5055527, KB5055528, KB5055547, KB5055557, KB5055581. Download from the Microsoft Update Catalog, or let Intune, Windows Update, or WSUS deliver it.
Which products are affected by CVE-2022-2601?
Azure Linux 3.0 ARM, Azure Linux 3.0 x64, CBL Mariner 1.0 ARM, Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows Server 2019.
Can I ask my own AI about CVE-2022-2601?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2022-2601's key facts: severity, CVSS, EPSS exploit probability, CISA KEV status, and the fixing KB. Copy it into Claude, ChatGPT, or Copilot for a triage plan; the data is refreshed three times a day (5 AM, 12:30 PM, and 7 PM US Central).
Fixed by the same updates
If you are patching CVE-2022-2601, the same updates also fix these:
Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.
