Urgent: Microsoft Fixes Nearly 400 Critical Security Holes
Microsoft’s August 2026 Patch Tuesday: What You Need to Know About 398 Security Fixes

Image: Shutterstock, Mallika Home Studio.
What Happened? (The Simple Version)
Imagine your house has 398 tiny cracks in the walls, windows, and doors. Some are hairline fractures. A few are big enough for a burglar to climb through. Microsoft just handed out repair kits for all of them at once.
On the second Tuesday of August 2026 (known as "Patch Tuesday"), Microsoft released security updates fixing 398 vulnerabilities in Windows and related software. This is the second month in a row with a massive patch bundle—July had over 570 fixes!
Patch Tuesday = The second Tuesday of every month when Microsoft releases security updates.
Reboot Wednesday = The day after, when everyone restarts their computers to apply those updates.
The Numbers at a Glance
| Category | Count | What It Means |
|---|---|---|
| Total vulnerabilities fixed | 398 | All shapes and sizes |
| Rated "Critical" | 42 | The "burglar-sized holes" — attackers could take over your PC remotely without you clicking anything |
| Actively exploited right now | 1 | A zero-day — bad guys are already using it |
| Publicly known before today | 2 | Researchers had already published details (so attackers knew too) |
The Three Most Important Bugs You Should Know About
1. The Active Zero-Day: CVE-2026-68820
- What it is: A flaw in
afd.sys— a core Windows driver that handles internet connections (think: the plumbing for all network traffic). - How attackers use it: They phish their way in (trick you into clicking a bad link), get a low-level foothold, then use this bug to become admin on your machine.
- Why it’s tricky: It’s a "race condition" — the exploit has to be timed perfectly, like threading a needle while on a rollercoaster. But attackers are landing it.
- Severity score: 7.0/10 (High)
2. The "Likely to Be Exploited" Bug: CVE-2026-62832
- Where: Windows User Profile Service (handles your login, settings, files).
- Backstory: Related to a public disclosure called "LegacyHive" by a researcher named Nightmare Eclipse.
- Risk: Microsoft says attackers will probably start using this soon.
3. The Publicly Known (But Lower Risk) Bug: CVE-2026-72971
- Type: Local tampering vulnerability.
- Good news: Microsoft says it’s unlikely to be exploited in the real world.
Why So Many Bugs All of a Sudden? Blame (and Thank) AI
Microsoft says artificial intelligence is helping researchers find vulnerabilities faster than ever. It’s like giving security teams a super-powered metal detector.
But here’s the catch: Everyone else is using AI too — including the bad guys. Other big companies are also shipping more patches:
- Adobe → Now patches twice a month (2nd & 4th Tuesdays)
- Cisco, Google, Mozilla, Oracle → All increasing patch frequency
Think of it like this: AI is great at finding holes in the fence. But fixing them? That’s still a human job.
Can AI Fix the Bugs It Finds? Not Reliably — Yet
Researchers at 1Password tested several AI models (LLMs) on writing patches for complex, newly disclosed vulnerabilities.
The results?
- More than half the time, the AI patch failed to fix the bug — or introduced a new bug (or both!).
Expert take:
Ed Skoudis (SANS Technology Institute): "AI is astonishingly good at finding vulnerabilities. Fixing them is a very different problem. Don’t expect one-shot AI patching to work. You need a skilled human at the keyboard — testing, iterating, verifying."
Tyler Reguly (Fortra): "Only 1 of 398 bugs is actively exploited right now. No need to rush. Test first. Deploy safe updates."
Expert Advice: Don’t Panic, Don’t Rush — Do This Instead
For IT Teams & Security Leaders
- Talk to your team — How are they handling the workload? Testing takes time.
- Support workflow changes — If they need more staging time, give it to them.
- Ignore vendor pressure — "Patch immediately!" sounds urgent, but a broken patch causes more downtime than a delayed one.
For Everyone (Yes, You at Home)
- Back up your data before applying updates.
- Wait a few days after Patch Tuesday — let Microsoft fix any buggy patches first.
- Apply updates within a week — don’t wait months.
Your 5-Step "Stay Safe" Checklist
- Backup first — External drive, cloud, or both.
- Wait 3–5 days after Patch Tuesday (let "Reboot Wednesday" chaos settle).
- Check for known issues — Search "[Month] Patch Tuesday problems" before installing.
- Apply updates — Let Windows Update do its thing.
- Reboot & verify — Make sure everything still works (printers, apps, VPN, etc.).
Summary
| Key Takeaway | Why It Matters |
|---|---|
| 398 flaws patched | Huge workload for IT; high volume is the "new normal" |
| 1 active zero-day (afd.sys) | Real attacks happening now — prioritize this fix |
| AI finds bugs faster | Patch volumes will keep growing |
| AI can’t reliably fix bugs yet | Humans still essential for safe patching |
| Don’t rush — test first | A bad patch breaks systems; a delayed patch just waits |
FAQ: Your Questions Answered
1. What is a "zero-day" vulnerability?
A zero-day is a security hole that attackers know about but the vendor (Microsoft) doesn’t — or hasn’t fixed yet. "Zero days" means the vendor has had zero days to prepare a patch. Once a patch exists, it’s no longer a zero-day.
2. What does "Critical" severity mean?
Microsoft’s highest rating. It means an attacker could remotely take control of your computer without you doing anything — no clicking, no opening files. Just being online is enough.
3. Should I install updates immediately on Patch Tuesday?
Not necessarily. Wait a few days. Sometimes patches have bugs (like breaking printers or causing blue screens). Microsoft usually fixes those quickly. Waiting 3–5 days is safer for most people.
4. What is afd.sys and why does it matter?
It’s a core Windows driver that manages network connections (sockets). Every time your PC talks to the internet — browsing, email, updates — afd.sys is involved. A bug here = deep system access for attackers.
5. Will AI eventually write perfect patches?
Maybe someday. But today, AI-generated patches fail over 50% of the time on complex bugs. Experts say human-in-the-loop is essential: AI suggests → human tests → AI improves → human verifies. We’re not at "set it and forget it" yet.
Want the full technical breakdown?
Check out the SANS Internet Storm Center’s per-patch roundup — clickable, filterable, and detailed.
Stay patched. Stay safe. And remember: a backed-up computer is a happy computer.