Windows Server 2012 R2: security updates (KB) and vulnerabilities

2 KB updates fix 4 tracked CVEs for Windows Server 2012 R2.

Windows Server 2012 R2 has 4 tracked vulnerabilities, 0 critical and 1 exploited in the wild (CISA KEV). A fixed release or vendor patch exists for 4. Most recent: 2026-10-13. Highest priority: CVE-2026-96951 (score 79/100).

• CVE-2026-96951 HIGH 8.8 EXPLOITED MITIGATE UPGRADE Microsoft Windows Command Injection Vulnerability
• CVE-2026-96960 HIGH 7.5 UPGRADE DOWNGRADE Asymmetric resource consumption (amplification) in .NET allows an unauthorized attacker to deny service over a
• CVE-2026-96959 HIGH 7.5 UPGRADE DOWNGRADE Allocation of resources without limits or throttling in .NET allows an unauthorized attacker to deny service o
• CVE-2026-108136 HIGH 7.8 UPGRADE UPGRADE Use after free in Microsoft Windows Search Component allows an authorized attacker to elevate privileges local

FAQ

How do I fix Windows Server 2012 R2 vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is Windows Server 2012 R2 being exploited right now?

Yes: 1 Windows Server 2012 R2 CVE is on the CISA Known Exploited Vulnerabilities list, so patch it first.

Which Windows Server 2012 R2 CVE should I patch first?

CVE-2026-96951 currently ranks highest (79/100): Microsoft Windows Command Injection Vulnerability.

Security updates (KB) for Windows Server 2012 R2

Install the KB from Windows Update, then verify with Get-HotFix -Id KBxxxxxxx or winver. Fixed build is the OS build number after the update.

← Back to latest CVEs