Article summary — original
Microsoft Releases Nearly 400 Security Updates Amid AI-Driven Vulnerability Surge
Microsoft has issued fixes for at least 398 security flaws in its August update release, driven by AI-assisted vulnerability discovery that is significantly increasing patch volumes across major software vendors.
The August batch fixes 398 vulnerabilities, including 42 critical flaws and an actively exploited privilege escalation zero-day (CVE-2026-68820) in the Windows afd.sys driver.
Microsoft and major vendors like Adobe, Cisco, Google, Mozilla, and Oracle are accelerating patch releases due to artificial intelligence finding security holes in software.
Research by 1Password indicates that large language models generated patches that either failed to fix flaws or introduced new vulnerabilities more than half the time.
Security experts advise organizations to test and pace deployments rather than rushing updates, as only one flaw in the current release is actively exploited.
August Patch Details and Exploited Zero-Day
Microsoft's August release remediates at least 398 vulnerabilities, 42 of which are rated critical because they allow attackers to gain remote control over systems with minimal user interaction. The release includes a single known zero-day vulnerability, CVE-2026-68820, which is an actively exploited privilege escalation flaw in the afd.sys driver that supports Windows socket connections. Attackers can use this flaw as a secondary step after gaining initial access to elevate privileges, relying on race conditions to take over the target system. Two additional flaws were publicly disclosed prior to the release: CVE-2026-62832 in the Windows User Profile Service and CVE-2026-72971, a low-impact local tampering issue.
The Impact and Limits of AI in Patching
The high volume of security fixes follows a record release of over 570 updates the previous month, a deluge Microsoft attributes to AI-assisted vulnerability discovery. Other software providers, such as Adobe, Cisco, Google, Mozilla, and Oracle, are also increasing update frequencies. However, while AI demonstrates strong capabilities in finding security flaws, utilizing it to write patches remains problematic. Research from 1Password showed that large language models produced flawed or harmful patches more than half the time when addressing complex vulnerabilities. SANS Technology Institute president Ed Skoudis emphasized that AI patch generation requires skilled human oversight, testing, and iterative improvement rather than reliance on automated one-shot fixes.
Deployment Strategy and System Safety
Security specialists warn against panic-driven patching despite the sheer volume of fixes. Tyler Reguly of Fortra highlighted that with only one flaw under active exploit, chief security officers should prioritize supporting IT teams through the rising workload and emphasize safe testing over hurried deployments. Administrators are also advised to back up systems and data before applying the substantial update package, potentially waiting a brief period to allow any initial patch defects to be resolved by Microsoft.
Saved original article
**Microsoft** today released updates to remedy at least 398 security vulnerabilities in its **Windows** operating systems and supported software, including one weakness that is already being actively exploited and two others that were publicly detailed prior to today.
August’s overstuffed bundle of patch joy from Microsoft did not eclipse its recording breaking release of [more than 570 security updates last month](https://krebsonsecurity.com/2026/07/microsoft-patches-a-record-570-security-flaws/), but it is double June’s then-record batch of [nearly 200 fixes](https://krebsonsecurity.com/2026/06/a-record-breaking-patch-tuesday-for-june-2026/#more-73788). Microsoft has attributed the recent patch deluge to vulnerability discoveries aided by artificial intelligence, and experts roundly agree that Windows users should get used to the idea of Patch Tuesdays (the second Tuesday of each month) covering hundreds of newly discovered security flaws.
Fully 42 of the 398 flaws that Microsoft patched today earned Redmond’s most-dire “critical” rating, meaning they are severe enough that malware or malcontents could exploit them to gain remote control over a Windows computer with little to no help from the user.
The sole known “zero day” bug fixed by Microsoft this month is [CVE-2026-68820](https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2026-68820), a privilege escalation weakness in a core Windows component called **afd.sys**, which the security firm **Automox** describes as “the driver behind Windows socket connections on effectively every endpoint.”
“This isn’t a front-door bug,” Automox’s **Landon Miles** [wrote](https://www.automox.com/blog/patch-fix-tuesday-august-2026) in a Patch Tuesday blog post. “It’s step two in a chain: an attacker phishes their way into a low-privilege foothold, then uses the driver flaw to take the box. The 7.0 score reflects the high attack complexity, because race conditions are fiddly. The exploit has to be thrown over and over until the timing lands. Someone is clearly landing it anyway.”
[CVE-2026-62832](https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2026-62832) is another privilege escalation flaw that Microsoft has labeled likely to be exploited; this flaw, in the Windows User Profile Service, may be related to the recent [“LegacyHive” public disclosure](https://www.theregister.com/security/2026/07/15/microsofts-serial-tormentor-drops-legacyhive-0-day/5271723) from the prolific bug hunter known as **Nightmare Eclipse**. The other publicly disclosed flaw is [CVE-2026-72971](https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2026-72971), a low-impact local tampering vulnerability that Microsoft reckons is unlikely to be exploited.
Other major software makers are likewise increasing their patch volumes and cadence thanks to AI, including **Adobe** which last month moved to twice-monthly security bulletins published on the 2nd and 4th Tuesday of each month. **Cisco**, **Google**, **Mozilla** and **Oracle** also are shipping updates far more frequently and abundantly.
By all accounts, AI is quite good at finding security holes in software. But for now at least, patching the resulting bugpocalypse remains a heavily human-centric endeavor, and the jury is still out on whether AI technologies will turn out to be as good at fixing vulnerabilities as they are at finding and exploiting them. This is an important question when one considers that these same AI technologies also are suggesting fixes for the vulnerabilities they find.
Researchers at **1Password** recently [examined](https://1password.com/blog/why-ai-generated-patches-still-require-human-review) what happens when different large language models (LLMs) generate vulnerability patches for newly disclosed, complex vulnerabilities. They found the LLMs produced patches that failed to fix the flaw or added a new weakness in the process (or both) more than half the time.
**Ed Skoudis**, president of the **SANS Technology Institute**, said his team has seen excellent results using AI to generate patches, provided there are humans in the loop to test the suggested fixes and push for iterative improvements.
“AI is rapidly becoming astonishingly good at finding vulnerabilities, but this research shows that fixing them is a very different problem,” Skoudis wrote in a SANS newsletter today. “Don’t expect one-shot AI patching to work reliably. Instead, iterate, test, challenge, improve, and verify. AI can be an extraordinary patching partner, but today it still needs a skilled human at the keyboard.”
**Tyler Reguly** at **Fortra** says while reports of Microsoft patching hundreds of vulnerabilities in one go have prompted some organizations to try to patch faster, it’s important to bear in mind that only one of the almost 400 bugs addressed today is known to be actively exploited. Reguly suggested security leaders check in with their teams to see how they’re handling the increasing workloads, which often involve testing fixes before deploying them in production environments.
“If you’re a chief security officer talk to your teams about how they are shifting or modifying their workflows to better accommodate the patching shift that we’re seeing and support them across various organizational units by enabling the changes they want to see made,” Reguly said. “There’s no need to rush these updates, no matter what various vendors and organizations try to tell you. You need to make sure that you are rolling out safe updates that will not negatively impact your systems.”
Speaking of the humans behind the keyboards, don’t neglect to backup your system and/or data before applying this month’s monster patch load. The day after each month’s Patch Tuesday is sometimes derisively referred to as Reboot Wednesday, but it generally doesn’t hurt to wait a few days to apply these huge update bundles because it sometimes takes a couple of days for the occasional misbehaving patch to get ironed out properly by Microsoft.
For a clickable, per-patch breakdown by severity and urgency, check out [this roundup](https://isc.sans.edu/diary/Microsoft%20Patch%20Tuesday%20August%202026/33236) from the SANS Internet Storm Center.