A Record-Breaking Year for Patch Tuesday

Microsoft’s August Patch Tuesday is here, and it’s a big one. The company has released fixes for at least 398 security vulnerabilities across Windows and supported software. That’s nearly double June’s then-record batch of around 200 fixes.

This month’s haul doesn’t quite top July’s staggering 570-plus updates, but it’s a clear sign that the era of small, manageable patch bundles is over. Microsoft attributes this surge to vulnerability discoveries powered by artificial intelligence. Security experts agree: get used to seeing hundreds of CVEs every month.

Critical Flaws and the Actively Exploited Zero-Day

Of the 398 flaws patched today, 42 are rated critical. That means they’re severe enough for attackers to potentially gain remote control over a Windows machine with minimal user interaction.

The one actively exploited zero-day is CVE-2026-68820, a privilege escalation vulnerability in afd.sys, the Windows socket driver. Landon Miles at Automox describes it as “the driver behind Windows socket connections on effectively every endpoint.”

Miles explains the attack chain: “An attacker phishes their way into a low-privilege foothold, then uses the driver flaw to take the box.” The vulnerability has a CVSS score of 7.0, reflecting the high attack complexity. Race conditions make the exploit fiddly, but someone is clearly landing it anyway.

Other Flaws to Watch

Two other vulnerabilities were publicly disclosed before today. CVE-2026-62832, a privilege escalation flaw in the Windows User Profile Service, is labeled likely to be exploited. It may be linked to the recent “LegacyHive” disclosure from researcher Nightmare Eclipse.

The other, CVE-2026-72971, is a low-impact local tampering bug that Microsoft considers unlikely to be exploited.

AI: Finding Bugs Faster Than We Can Fix Them

Microsoft isn’t alone in this AI-driven patch deluge. Adobe has moved to twice-monthly security bulletins. Cisco, Google, Mozilla, and Oracle are all shipping updates more frequently and in larger volumes.

AI is undeniably good at finding security holes. But fixing them? That’s another story. Researchers at 1Password tested how well large language models generate patches for complex, newly disclosed vulnerabilities. The results were sobering: more than half the time, the AI-generated patches either failed to fix the flaw or introduced a new weakness. Sometimes both.

Ed Skoudis, president of the SANS Technology Institute, has seen promising results with AI-assisted patching — but only with humans in the loop. “AI is rapidly becoming astonishingly good at finding vulnerabilities, but this research shows that fixing them is a very different problem,” he wrote. “Don’t expect one-shot AI patching to work reliably. Instead, iterate, test, challenge, improve, and verify.”

Should You Rush to Patch?

With nearly 400 fixes, it’s tempting to deploy everything immediately. Tyler Reguly at Fortra advises against panic. Only one of these bugs is known to be actively exploited right now.

Reguly suggests security leaders check in with their teams about workload and workflow. “There’s no need to rush these updates,” he says. “You need to make sure that you are rolling out safe updates that will not negatively impact your systems.”

That means testing patches before deployment, especially in production environments. A broken patch can be worse than the vulnerability it’s meant to fix.

Practical Steps for Home Users and Admins

• Back up your system before applying this month’s updates. The day after Patch Tuesday is sometimes called “Reboot Wednesday,” but it’s wise to wait a few days.
• Prioritize the zero-day: CVE-2026-68820 should be at the top of your list.
• Test before deploying in enterprise environments. Microsoft sometimes needs a couple of days to iron out misbehaving patches.
• Monitor the SANS Internet Storm Center for a clickable, per-patch breakdown by severity and urgency.

For more on how to handle these massive update bundles, check out our guide to Windows update management best practices. And if you’re worried about AI-generated vulnerabilities, read about AI security risks in 2026.

The bottom line: patch, but patch smart. The volume is only going to grow.

A $36 Million Bet on AI-Driven Email Defense

Email security startup AegisAI has secured $36 million in a Series A round led by Battery Ventures, with participation from Accel and Foundation Capital. The announcement came Thursday, bringing the company’s total raised to $49 million since its founding in 2025.

The fresh capital isn’t just a milestone—it’s fuel for a specific mission. AegisAI plans to expand its lineup of autonomous detection agents, push its Vanguard agent toward general availability, and scale its enterprise go-to-market efforts. In plain terms: they’re gearing up for a serious fight against a new breed of cyber threat.

From Google’s Security Team to Email’s Front Lines

AegisAI was founded by Cy Khormaee and Ryan Luo, two veterans of Google’s security team who helped build reCAPTCHA, Safe Browsing, and Web Risk. The company emerged from stealth in September 2025 with a clear thesis: traditional email security is no match for AI-powered attacks.

Their platform is built around a network of AI agents that scrutinize incoming email for phishing, business email compromise, and other threats. Instead of relying on static rules or known-bad signatures, the system evaluates the intent and identity behind each message. It’s a fundamental shift from the blocklist-and-keyword approach that has dominated the industry for decades.

How Vanguard Investigates Threats Like a Human

The product connects to Microsoft 365 and Google Workspace through an API, requiring no changes to a customer’s MX records. That’s a deliberate choice—deployment friction is often the death of security tools, and AegisAI clearly wants to avoid that trap.

In March, the company introduced Vanguard, a companion agent that takes a more proactive approach. It investigates suspicious links and attachments by navigating to them the way a human recipient would, then compiles a threat report within minutes. This mimics the curiosity of a cautious employee—but at machine speed.

The Rise of AI Spear Phishing

AegisAI frames its work around what it calls AI spear phishing: attacks that use language models to research a target, map their professional relationships, and produce a personalized lure at a fraction of the cost such an effort once required. The economics of attack have changed, and so must the defense.

Why Human Training Isn’t Enough

Khormaee, who serves as CEO, didn’t mince words about the threat landscape. “The most immediate, catastrophic risk to your organization isn’t an AI agent hacking your firewall. It’s an AI model manipulating someone in your organization into handing over the keys,” he said.

His critique of traditional security awareness programs is pointed: “If your security program still relies on template-based phishing tests and awareness training, you are training your people to spot last year’s threat, not a capable agent crafting a novel lure just for them.” His conclusion is stark—”When the attack is AI, the defense has to be AI.”

What This Means for the Email Security Market

The funding round signals growing investor confidence in AI-native security solutions. Battery Ventures’ leadership role is notable, given the firm’s history of backing enterprise infrastructure companies. With Accel and Foundation Capital also on board, AegisAI has the backing of three heavyweight investors who clearly see a gap in the market.

The $49 million total funding gives the startup runway to compete with established players in the email security space. But the real test will be whether its AI agents can consistently catch threats that slip past traditional filters—and whether enterprises are ready to trust an AI to guard their inboxes.

For CISOs watching the space, the takeaway is clear: the email security landscape is shifting, and the next generation of tools will look very different from what came before. Whether that’s a good thing depends on how well companies like AegisAI deliver on their promises.

USB Auto-Install: The Unexpected Attack Surface

Plugging in a USB stick feels routine. You expect a quick notification and maybe a driver install. But a team of researchers just turned that mundane process into a full SYSTEM-level compromise on a fully patched Windows 11 machine.

The attack abuses Windows Plug and Play (PnP) to fetch signed vendor software for an emulated USB device. Then it chains privileged installation components to escalate straight to SYSTEM. No zero-day kernel exploits. No password cracking. Just the trust Windows places in signed drivers and its own auto-install logic.

Here’s the scary part: the same PnP path works over Remote Desktop, no physical hardware required — provided Plug and Play or low-level USB redirection is enabled.

How the Windows 11 USB Attack Chain Works

The attack starts with a malicious or emulated USB device that presents itself as legitimate hardware. Windows PnP queries the device, looks for a matching signed driver package, and downloads it from Windows Update or the vendor’s server.

That’s by design. But the researchers found a way to hijack the process mid-stream. Here’s the breakdown:

• Emulated device: The attacker crafts a USB descriptor that mimics a real peripheral, like a network adapter or printer.
• Driver fetch: Windows PnP automatically retrieves a signed vendor driver for the emulated device.
• Privileged component: The driver package includes an installer or utility that runs with elevated privileges.
• SYSTEM escalation: The attacker exploits that privileged execution to drop a payload with SYSTEM rights.

The chain is elegant because it never triggers a UAC prompt. Windows trusts its own PnP pipeline, and the vendor’s signature validates the package as safe.

Remote Desktop USB Redirection Expands the Threat

Physical access was once the limiting factor for USB attacks. The researchers removed that barrier. With Remote Desktop’s Plug and Play redirection or low-level USB redirection enabled, an attacker can trigger the same PnP path remotely.

That means a compromised RDP session — or a malicious admin on the same network — could deliver the emulated USB device virtually. The victim’s Windows 11 machine would fetch the signed driver, run the privileged installer, and hand over SYSTEM access without ever touching a physical port.

Microsoft’s response? The company says the behavior is by design, noting that the attack requires either physical access or an already-compromised RDP session. That’s cold comfort for anyone relying on USB redirection for remote work.

Why Signed Drivers Make This Hard to Stop

Vendor signatures are the crown jewel of Windows driver trust. They tell the OS, “This code is safe to run.” The researchers didn’t break that trust — they weaponized it.

By using a legitimate signed driver’s installer, the attack avoids the usual red flags. Antivirus tools see a valid signature and often skip deep inspection. The result: a stealthy privilege escalation that evades detection.

Mitigations for Windows 11 USB PnP Attacks

There’s no magic patch coming, since Microsoft views this as intended functionality. But you can reduce your exposure:

• Disable USB redirection in Remote Desktop settings unless absolutely necessary.
• Restrict PnP device installation via Group Policy to approved device classes.
• Monitor driver installation events in Event Viewer for unexpected signed driver activity.
• Use device control software to block unauthorized USB devices at the endpoint.
• Limit RDP access to trusted users and networks, and enforce strong authentication.

For most organizations, the biggest win is locking down RDP USB redirection. It’s a feature few users genuinely need, and it’s the easiest remote path to this attack.

What This Means for Windows Security

This research is another reminder that Windows’ convenience features are attack surface. Plug and Play was designed for a world where physical trust was assumed. That assumption no longer holds.

We’ve seen similar issues with Windows driver signature bypass techniques and privilege escalation via legitimate services. The pattern is consistent: attackers abuse what Windows trusts, not what it fails to secure.

For defenders, the takeaway is practical. Audit your RDP configuration. Review driver installation policies. And remember that a signed driver is not a guarantee of safety — it’s just a promise from a vendor who might not know how their installer is being abused.

The researchers’ full technical details remain limited, but the proof-of-concept is clear: Windows 11 USB auto-install is no longer just a convenience. It’s a potential backdoor.