Microsoft's December Patch Tuesday Fixes Over 1,250 Bugs, Including Actively Exploited Outlook Flaw
Microsoft's latest Patch Tuesday release addressed 1,259 vulnerabilities across its product portfolio, the second consecutive month the company has issued patches exceeding 1,000 flaws. Of these, 726 affect Windows components. Among the fixes is a patch for an Outlook vulnerability that is already being exploited in the wild and can be abused to expose NTLMv2 password hashes.
NTLMv2 is a legacy Windows authentication protocol still widely used for backward compatibility in enterprise environments. Vulnerabilities that leak NTLMv2 hashes are particularly dangerous because attackers can capture these hashes and attempt offline cracking or relay them to authenticate as the victim on other systems, a technique known as an NTLM relay attack. Outlook has historically been a frequent target for such flaws, since certain email or calendar content can trigger automatic authentication attempts without requiring the user to open an attachment or click a link, making exploitation unusually stealthy.
The sheer scale of this month's patch batch reflects a broader trend of rising vulnerability disclosure volumes across major vendors, driven by expanding product surfaces, increased security research scrutiny, and growing use of automated vulnerability discovery tools. While most of the 1,259 fixes address issues of varying severity across Windows and other Microsoft products, the presence of an actively exploited zero-day significantly raises the urgency of this release compared to a routine patch cycle.
Actively exploited vulnerabilities, especially those enabling credential theft, pose an outsized risk because attackers already possess working exploits before organizations have had a chance to patch. Once NTLMv2 hashes are captured, adversaries can potentially move laterally across a network, escalate privileges, or compromise additional systems, turning a single email-based flaw into a broader intrusion.
Security teams should prioritize deploying this month's Outlook patch immediately given its confirmed exploitation status, and more broadly assess exposure to NTLM authentication across their environment. Where feasible, organizations should disable NTLM in favor of Kerberos, enable SMB signing and Extended Protection for Authentication, and monitor for anomalous authentication attempts, while also ensuring a structured process is in place to rapidly triage and deploy the remainder of this month's large patch set based on exploitability and asset criticality.
Source: The Hacker News
Read the original report ↗This is an original summary written by CyberSkii for reference. All rights to the underlying reporting remain with the publisher linked above.