# Hackers are already exploiting the Windows zero-day Microsoft just patched

> Microsoft patched Windows zero-day CVE-2026-68820 this week, but attackers are already exploiting it, and a Cisco ASA VPN flaw is under attack too.

- Published: 2026-08-15
- Topic: [Security](https://futuretechnologyhq.com/topic/security/)
- URL: https://futuretechnologyhq.com/article/windows-zero-day-cve-2026-68820-august-patch-tuesday/
- Publisher: [Future Technology HQ](https://futuretechnologyhq.com/), free to read. Quote as "Future Technology HQ" with a link to the article.

## Key points

- CVE-2026-68820 is a Windows privilege escalation flaw in the WinSock driver, rated CVSS 7.0 and already exploited in the wild
- A separate Cisco ASA and FTD SSL VPN vulnerability lets unauthenticated attackers crash devices remotely
- Both fixes are available now, and both flaws are under active attack, so patching is a this-weekend job

## Article

Microsoft shipped a fix for CVE-2026-68820 in this week's Patch Tuesday, its monthly security update day. Attackers had already been using the flaw for a while, which makes it a zero-day: a vulnerability exploited before a patch exists.

The bug sits in the Windows Ancillary Function Driver for WinSock, the kernel-level component that handles network socket calls for effectively every application on a Windows machine. It carries a CVSS score of 7.0 on the 10 point scale, which reads as moderate right up until you notice the "exploited in the wild" label sitting next to it. A Cisco ASA VPN flaw is also under attack this week, and both fixes are available now.

## What is CVE-2026-68820?

CVE-2026-68820 is a privilege escalation vulnerability in the Windows Ancillary Function Driver for WinSock, usually shortened to AFD. WinSock is the Windows interface that applications use to open network connections, send data and receive it. The driver sits in the kernel, the most trusted part of the operating system, so a mistake there can hand an attacker far more power than a bug in an ordinary application.

CVSS, the Common Vulnerability Scoring System, rates the technical severity of a flaw. A score of 7.0 lands in the "high" band, but the number says nothing about whether anyone is using the flaw. Here, someone is. Microsoft flagged it as exploited in the wild when it shipped the fix on 11 August, and CISA added it to its Known Exploited Vulnerabilities catalogue the same day.

## What does this Windows zero-day actually buy an attacker?

Privilege escalation is not how someone breaks into your network. It is what they do once they are already standing in the hallway. A phishing click or a stolen credential gets an attacker onto a machine as a normal user. CVE-2026-68820 is the step that turns that limited foothold into SYSTEM-level control of the box.

SYSTEM is the highest privilege level on a Windows machine. With it, an attacker can switch off security tools, read memory to lift stored passwords, install persistent software and move on to other machines. A normal user account can do almost none of that.

That distinction matters for how you triage it. On its own, a 7.0 privilege escalation bug is unremarkable. Chained behind an initial access technique, it is the difference between one compromised laptop and a domain-wide incident. That is exactly why it shows up in real attacks rather than proof-of-concept demos, and it is the same pattern we saw with [the Metabase zero-day earlier this month](/article/metabase-zero-day-august-2026/).

### Why attackers favour kernel drivers

Kernel components like AFD run with full trust and parse data from every networked application, which gives researchers and attackers a large surface to probe. Local privilege escalation bugs in drivers like this are a staple of intrusion toolkits because they are reliable once found and need no further user interaction after the first foothold.

The same bug number has appeared elsewhere in our coverage. [Lazarus used a Windows zero-day to drop a kernel rootkit on aerospace firms](/article/lazarus-windows-zero-day-cve-2026-68820/), and that story carries the same CVE identifier. It shows the kind of use a flaw like this attracts once it is known.

## What is the Cisco problem running alongside it?

Microsoft is not the only vendor with an active problem this week. A vulnerability in Cisco ASA and FTD SSL VPN appliances is also being exploited, and this one does not need credentials at all. ASA is Cisco's Adaptive Security Appliance firewall line, and FTD is Cisco's Firepower software that runs on Cisco's newer firewalls.

An unauthenticated attacker can crash the device remotely. For most organisations that means the VPN concentrator the entire remote workforce depends on goes offline. Nobody needs to steal data for that to hurt: staff cannot reach internal systems, and the security team is pulled away from other work to restore service.

Two actively exploited flaws in the same week, sitting at opposite ends of the stack: one in Windows desktops, one in the network edge appliance in front of them. Almost every organisation of any size runs at least one of those.

## How do the two flaws compare?

The two problems affect different layers and call for different urgency. This table sets them side by side.

| | Windows CVE-2026-68820 | Cisco ASA and FTD SSL VPN flaw |
|---|---|---|
| Where it sits | Ancillary Function Driver for WinSock | SSL VPN service on ASA and FTD appliances |
| Type | Privilege escalation to SYSTEM | Remote crash (denial of service) |
| Attacker needs | A foothold as a normal user | No credentials at all |
| Reach | Local, chained after initial access | Remote, over the internet |
| Status | Exploited in the wild, patched | Under attack, fix available |
| Worst case | Domain-wide compromise | Remote workforce locked out |

The Windows bug is the more dangerous one inside a network. The Cisco bug is the easier one to hit from outside it, which affects the order in which you should fix them.

## What should you do this weekend?

Patch the Cisco appliances first. An unauthenticated remote crash on an internet-facing device is a lower-effort attack than a chained privilege escalation, and the blast radius is your entire remote access path.

Then push the Windows updates through your normal ring deployment, which means updating a small pilot group first and widening out in stages, but compress the timeline. "Next month's maintenance window" is not a plan for something already in use.

A short checklist helps:

- Confirm which Cisco ASA and FTD devices expose SSL VPN to the internet, and update those first.
- Approve the August Windows cumulative update for all supported machines, starting with servers and admin workstations.
- Check logs for unexpected SYSTEM-level process starts and for repeated VPN service restarts.
- Record any machine that cannot be patched this week, and add extra monitoring to it.

### What if you cannot patch yet?

If you are running either product and have no patch window until September, assume exposure and monitor accordingly. Ransomware crews move fast on exactly this kind of bug, and [attacks on large organisations have been climbing all year](/article/ransomware-attacks-billion-dollar-companies-surge-2026/). The gap between a public patch and mass exploitation is usually measured in days, not weeks, as [last month's Oracle and SonicWall round showed](/article/oracle-july-2026-cpu-sonicwall-sma1000/).

Patch deadlines are getting shorter for the same reason. We covered [how CISA cut the patch window to three days](/article/cisa-three-day-patch-window/), and the logic applies to ordinary businesses as much as to federal agencies: once a flaw is public and in use, every extra day is a day of open exposure.

## What happens next?

Expect more detail to emerge now that the patch is out. Once a fix ships, researchers compare the old and new driver code to find exactly what changed, and that comparison tends to produce public exploit code for anyone willing to use it. A flaw already used by a few attackers can then become available to many more.

For defenders, the practical sequence is simple. Apply the fixes, watch for signs that someone got in before you did, and treat any machine that stayed unpatched while the flaw was being used as one that deserves a closer look. The monthly [Patch Tuesday](/article/microsoft-august-2026-patch-tuesday-421-cves/) cycle is a rhythm, but attackers do not wait for it.

## Key takeaways

- CVE-2026-68820 is a Windows privilege escalation flaw in the Ancillary Function Driver for WinSock, rated CVSS 7.0, and it was exploited in the wild before Microsoft patched it.
- The flaw lets an attacker who already has a normal user foothold gain SYSTEM-level control of the machine.
- A separate Cisco ASA and FTD SSL VPN vulnerability is also under attack and lets unauthenticated attackers crash devices remotely.
- Patch the Cisco appliances first, because an internet-facing crash bug is easy to exploit and takes the whole remote access path offline.
- Both fixes are available now, so patching is a this-weekend job rather than something for next month's window.

## Sources

- [Tenable](https://www.tenable.com/cve/CVE-2026-68820)
- [BleepingComputer](https://www.bleepingcomputer.com/news/security/cisco-warns-of-asa-and-ftd-vpn-flaw-exploited-to-crash-devices/)
