Patch tracker / CVE reference / CVE-2022-2601

CVE-2022-2601

CVE-2022-2601 is a high severity Microsoft vulnerability with a CVSS score of 8.6. Its EPSS score puts the probability of exploitation in the next 30 days at 41%. Microsoft has shipped the fix: deploy the update below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

8.6

CVSS

41%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 41%. CVSS 8.6 (High).

This CVE is among the top half of tracked Microsoft CVEs by EPSS exploit probability.

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.

I am an IT admin assessing a vulnerability. Facts for CVE-2022-2601 (source: https://senserva.com/cve/CVE-2022-2601.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2022-2601: High severity Microsoft vulnerability, CVSS 8.6
- EPSS 30-day exploitation probability: 41%
- Actively exploited (CISA KEV): no
- Fixed by: KB5041592
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch this cycle

Not confirmed exploited yet, but the 30-day exploit probability is high (EPSS 41%).

Fixed by KB5041592. Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Patch in this maintenance window; do not let it slip to the next one.

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 update KB5041592 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security update 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.

KB5041592

Scope and sources

Affected products

Fixed by the same update

CVE-2024-38106 CVE-2024-38107 CVE-2024-38178 CVE-2024-38193 CVE-2024-38140 CVE-2024-38143 CVE-2024-38199 CVE-2024-38114

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.