Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is BlueKeep?

BlueKeep is CVE-2019-0708, a wormable pre-authentication remote code execution flaw in Windows Remote Desktop Services that Microsoft patched even for Windows XP in May 2019.

Illustration for the cybersecurity term BlueKeep
Home / Blog / Cybersecurity Terms / What Is BlueKeep?
17 November 2026

What Is BlueKeep?

What Is BlueKeep?

BlueKeep is the name given to CVE-2019-0708, a remote code execution vulnerability in Windows Remote Desktop Services disclosed by Microsoft on 14 May 2019. It requires no authentication and no user interaction: a single sequence of packets to TCP port 3389 is enough to run code with SYSTEM privileges. Microsoft rated it wormable and took the unusual step of issuing patches for Windows XP and Windows Server 2003, both long out of support.

The NSA, the NCSC, and CISA all published separate advisories urging organisations to patch. For several months in 2019 BlueKeep was widely expected to produce a WannaCry-scale event. It did not, and understanding why is as instructive as the vulnerability itself.

The Technical Flaw

Remote Desktop Services creates a set of static virtual channels when a connection is established. One of them, named MS_T120, is reserved for internal use and is normally bound to channel 31. The RDP driver did not validate that a client could not request this name for a different channel. An attacker who bound MS_T120 to another channel index and then triggered its cleanup caused a use-after-free in kernel memory inside termdd.sys. Carefully shaped heap grooming turned that into reliable kernel code execution.

Affected versions are Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows XP, and Windows Server 2003. Windows 8 and later reworked the channel handling and are unaffected.

What Actually Happened

Scans in May 2019 found roughly one million internet-facing hosts responding to RDP and vulnerable. Exploit development proved harder than expected; the publicly available proof of concept code was unstable and tended to blue-screen the target. A working Metasploit module for Windows 7 and Server 2008 R2 arrived in September 2019.

Mass exploitation began in early November 2019, when honeypots run by the researcher Kevin Beaumont started crashing. The campaign installed a Monero cryptomining payload and was not worm-based at all: it sprayed the exploit across the internet from a fixed set of hosts, and the crashes happened because the exploit was unreliable. The anticipated self-propagating worm never materialised, largely because kernel exploitation across varied hardware and patch levels is genuinely difficult to make stable.

Why It Still Comes Up

BlueKeep remains on CISA’s Known Exploited Vulnerabilities catalogue and still appears in external scan reports. The reason is rarely an unpatched Windows 7 desktop on the public internet. It is usually one of:

In other words, BlueKeep is now less a vulnerability than an asset management indicator. A host that is still vulnerable in 2026 has been outside patch management for years, and whatever else is wrong with it is likely to be worse.

Remediation

Detecting Exposure and Exploitation

Scan internal and external ranges for port 3389, not just the perimeter, and check build numbers rather than trusting the asset database. For exploitation, watch for unexpected RDP connections to legacy hosts, for termdd.sys or RDP service crashes, and for new services or scheduled tasks appearing on machines that should be quiet. Related RDP-specific events, including failed channel binds, are recorded in the TerminalServices operational logs.

If you are not sure what is still listening on 3389 across your estate, our continuous vulnerability scanning services will tell you, and keep telling you.

FAQ – Frequently Asked Questions

Which Windows Versions Are Vulnerable to BlueKeep?

Windows XP, Windows Server 2003, Windows 7, Windows Server 2008, and Windows Server 2008 R2. Windows 8, Windows 10, Windows 11, and the corresponding server releases are not affected, because the virtual channel handling was rewritten. Microsoft issued patches for the unsupported versions as well, which is rare and reflects how serious the risk was considered.

Does Network Level Authentication Fix BlueKeep?

It mitigates it rather than fixing it. With Network Level Authentication enabled, a client must authenticate before the vulnerable channel setup takes place, so an unauthenticated attacker cannot reach the flaw. An attacker with valid credentials still can. Enable it as a defence in depth measure, but patch the system and remove its exposure to untrusted networks as well.

Why Was There Never a BlueKeep Worm?

Reliable kernel exploitation across different hardware, memory layouts, and patch levels is hard, and the public exploits frequently crashed targets instead of taking control. The November 2019 campaign that did use it was a conventional mass-scanning operation deploying a cryptominer, not self-propagating code. The lesson is that wormability is a judgement about potential, not a prediction.

Should I Still Scan for BlueKeep?

Yes, as an indicator rather than a target. Any host still vulnerable has not received a Windows update since 2019, which means it has dozens of other unpatched flaws. Finding it tells you something important about coverage gaps in your asset inventory and patching process, particularly for virtual machines, embedded systems, and supplier-managed equipment.

Related Terms

You May Be Interested In These

What Is ProxyShell?

Cybersecurity Terms

17 November 2026

What Is ProxyShell?

Read More
What Is AES Encryption?

Cybersecurity Terms

17 November 2026

What Is AES Encryption?

Read More