CVE-2019-0708

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 3 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 100%CVSS: 9.8Exploit: cisa kev · ssvc active · kev ransomware · Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A remote code execution vulnerability exists in Remote Desktop Services formerly known as Terminal Services when an unauthenticated attacker connects to the target system using RDP and sends specially crafted requests, aka 'Remote Desktop Services Remote Code Execution Vulnerability'.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
99(Act)
EG Risk 99/100SSVC: Act

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation100% × 40%
Automatability100% × 15%
Action: Fix now — active exploitation, automatable, high impact.
EPSS PROB
100%
EPSS %ILE
100%
KEV
⚠ Exploited

Published

May 16, 2019

Last Modified

June 17, 2026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 76× in last 7d / 288× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 876 total refreshes for this CVE.

  1. 2026-08-21 19:04 UTCGHSA enrichment
  2. 2026-08-21 16:49 UTCCISA KEV update
  3. 2026-08-21 14:44 UTCGHSA enrichment
  4. 2026-08-21 10:24 UTCVendor advisory
  5. 2026-08-21 10:24 UTCGHSA enrichment
  6. 2026-08-21 06:05 UTCVendor advisory
  7. 2026-08-21 06:05 UTCGHSA enrichment
  8. 2026-08-21 01:45 UTCVendor advisory
  9. 2026-08-21 01:44 UTCGHSA enrichment
  10. 2026-08-20 21:25 UTCVendor advisory
  11. 2026-08-20 21:25 UTCGHSA enrichment
  12. 2026-08-20 17:06 UTCCISA KEV update
  13. 2026-08-20 17:06 UTCVendor advisory
  14. 2026-08-20 17:06 UTCGHSA enrichment
  15. 2026-08-20 12:47 UTCVendor advisory
  16. 2026-08-20 12:47 UTCGHSA enrichment
  17. 2026-08-20 08:28 UTCVendor advisory
  18. 2026-08-20 08:28 UTCGHSA enrichment
  19. 2026-08-20 04:09 UTCGHSA enrichment
  20. 2026-08-19 23:50 UTCVendor advisory
  21. 2026-08-19 23:50 UTCGHSA enrichment
  22. 2026-08-19 19:30 UTCVendor advisory
  23. 2026-08-19 19:30 UTCGHSA enrichment
  24. 2026-08-19 17:33 UTCCISA KEV update
  25. 2026-08-19 15:10 UTCVendor advisory
Show 75 more
  1. 2026-08-19 15:10 UTCGHSA enrichment
  2. 2026-08-19 10:51 UTCVendor advisory
  3. 2026-08-19 10:51 UTCGHSA enrichment
  4. 2026-08-19 06:31 UTCVendor advisory
  5. 2026-08-19 06:31 UTCGHSA enrichment
  6. 2026-08-19 02:11 UTCVendor advisory
  7. 2026-08-19 02:11 UTCGHSA enrichment
  8. 2026-08-18 21:51 UTCVendor advisory
  9. 2026-08-18 21:51 UTCGHSA enrichment
  10. 2026-08-18 17:32 UTCVendor advisory
  11. 2026-08-18 17:32 UTCGHSA enrichment
  12. 2026-08-18 16:58 UTCCISA KEV update
  13. 2026-08-18 13:12 UTCVendor advisory
  14. 2026-08-18 13:12 UTCGHSA enrichment
  15. 2026-08-18 08:52 UTCGHSA enrichment
  16. 2026-08-18 04:32 UTCGHSA enrichment
  17. 2026-08-18 00:13 UTCVendor advisory
  18. 2026-08-18 00:13 UTCGHSA enrichment
  19. 2026-08-17 19:52 UTCVendor advisory
  20. 2026-08-17 19:52 UTCGHSA enrichment
  21. 2026-08-17 15:33 UTCVendor advisory
  22. 2026-08-17 15:33 UTCGHSA enrichment
  23. 2026-08-17 13:56 UTCCISA KEV update
  24. 2026-08-17 11:13 UTCVendor advisory
  25. 2026-08-17 11:13 UTCGHSA enrichment
  26. 2026-08-17 06:54 UTCVendor advisory
  27. 2026-08-17 06:54 UTCGHSA enrichment
  28. 2026-08-17 02:35 UTCVendor advisory
  29. 2026-08-17 02:35 UTCGHSA enrichment
  30. 2026-08-16 22:16 UTCVendor advisory
  31. 2026-08-16 22:16 UTCGHSA enrichment
  32. 2026-08-16 17:56 UTCVendor advisory
  33. 2026-08-16 17:56 UTCGHSA enrichment
  34. 2026-08-16 13:36 UTCVendor advisory
  35. 2026-08-16 13:36 UTCGHSA enrichment
  36. 2026-08-16 09:17 UTCVendor advisory
  37. 2026-08-16 09:17 UTCGHSA enrichment
  38. 2026-08-16 04:58 UTCVendor advisory
  39. 2026-08-16 04:58 UTCGHSA enrichment
  40. 2026-08-16 00:39 UTCVendor advisory
  41. 2026-08-16 00:39 UTCGHSA enrichment
  42. 2026-08-15 20:20 UTCVendor advisory
  43. 2026-08-15 20:20 UTCGHSA enrichment
  44. 2026-08-15 16:01 UTCVendor advisory
  45. 2026-08-15 16:01 UTCGHSA enrichment
  46. 2026-08-15 11:42 UTCVendor advisory
  47. 2026-08-15 11:42 UTCGHSA enrichment
  48. 2026-08-15 07:23 UTCVendor advisory
  49. 2026-08-15 07:23 UTCGHSA enrichment
  50. 2026-08-15 03:04 UTCVendor advisory
  51. 2026-08-15 03:04 UTCGHSA enrichment
  52. 2026-08-14 22:44 UTCVendor advisory
  53. 2026-08-14 22:44 UTCGHSA enrichment
  54. 2026-08-14 18:25 UTCVendor advisory
  55. 2026-08-14 18:25 UTCGHSA enrichment
  56. 2026-08-14 14:06 UTCVendor advisory
  57. 2026-08-14 14:06 UTCGHSA enrichment
  58. 2026-08-14 09:46 UTCGHSA enrichment
  59. 2026-08-14 05:27 UTCVendor advisory
  60. 2026-08-14 05:27 UTCGHSA enrichment
  61. 2026-08-14 01:08 UTCVendor advisory
  62. 2026-08-14 01:08 UTCGHSA enrichment
  63. 2026-08-13 20:48 UTCVendor advisory
  64. 2026-08-13 20:48 UTCGHSA enrichment
  65. 2026-08-13 16:29 UTCVendor advisory
  66. 2026-08-13 16:29 UTCGHSA enrichment
  67. 2026-08-13 12:10 UTCVendor advisory
  68. 2026-08-13 12:10 UTCGHSA enrichment
  69. 2026-08-13 07:50 UTCVendor advisory
  70. 2026-08-13 07:50 UTCGHSA enrichment
  71. 2026-08-13 03:31 UTCGHSA enrichment
  72. 2026-08-12 23:12 UTCGHSA enrichment
  73. 2026-08-12 18:53 UTCVendor advisory
  74. 2026-08-12 18:53 UTCGHSA enrichment
  75. 2026-08-12 14:34 UTCVendor advisory

Publicly available exploits

(10 references)

Working exploit code is in the public domain (1 Metasploit module) (5 GitHub PoCs) (4 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCRICSecLab/CVE-2019-0708
    First seen Mar 15, 2020

    CVE-2019-0708 (BlueKeep) proof of concept allowing pre-auth RCE on Windows7

    Open source ↗
  • GitHub PoCcbwang505/CVE-2019-0708-EXP-Windows
    First seen Jan 21, 2020

    CVE-2019-0708-EXP-Windows版单文件exe版,运行后直接在当前控制台反弹System权限Shell

    Open source ↗
  • Exploit-DBEDB-47683
    First seen Nov 19, 2019

    Microsoft Windows 7 (x86) - 'BlueKeep' Remote Desktop Protocol (RDP) Remote Windows Kernel Use After Free

    Open source ↗
  • GitHub PoCCyb0r9/ispy
    First seen Sep 30, 2019

    ispy V1.0 - Eternalblue(ms17-010)/Bluekeep(CVE-2019-0708) Scanner and exploit ( Metasploit automation )

    Open source ↗
  • Exploit-DBEDB-47416✓ verified
    First seen Sep 24, 2019

    Microsoft Windows - BlueKeep RDP Remote Windows Kernel Use After Free (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/rdp/cve_2019_0708_bluekeep_rce✓ verified
    First seen Sep 6, 2019

    Pre-auth RDP RCE on Windows 7/Server 2008. Production-grade Metasploit module.

    Open source ↗
  • GitHub PoC0xeb-bp/bluekeep
    First seen Jul 23, 2019

    Public work for CVE-2019-0708

    Open source ↗
  • Exploit-DBEDB-47120
    First seen Jul 15, 2019

    Microsoft Windows Remote Desktop - 'BlueKeep' Denial of Service (Metasploit)

    Open source ↗
  • GitHub PoCalgo7/bluekeep_CVE-2019-0708_poc_to_exploit
    First seen May 31, 2019

    An Attempt to Port BlueKeep PoC from @Ekultek to actual exploits

    Open source ↗
  • Exploit-DBEDB-46946
    First seen May 30, 2019

    Microsoft Windows Remote Desktop - 'BlueKeep' Denial of Service

    Open source ↗

Past incidents using this CVE

(1)

This CVE was central to one or more publicly-documented breaches. Each card links to authoritative reporting at the time of the incident.

  • BlueKeep (Windows RDP)May 2019

    Wormable Remote Desktop Protocol pre-auth RCE on Windows 7/Server 2008. Microsoft took the unusual step of patching out-of-support Windows XP. Mass-scanning began within days.

    Source: KrebsOnSecurity

Frequently asked(6)

What is CVE-2019-0708?
CVE-2019-0708 is a critical vulnerability published on May 16, 2019. A remote code execution vulnerability exists in Remote Desktop Services formerly known as Terminal Services when an unauthenticated attacker connects to the target system using RDP and sends specially crafted requests, aka 'Remote Desktop Services Remote Code Execution Vulnerability'.
When was CVE-2019-0708 disclosed?
CVE-2019-0708 was first published in the National Vulnerability Database on May 16, 2019, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-0708 actively exploited?
Yes. CISA added CVE-2019-0708 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft Remote Desktop Services. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2019-0708?
CVE-2019-0708 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2019-0708?
CVE-2019-0708 affects Microsoft Remote Desktop Services. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2019-0708?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0708, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-0708

Explore →

Is Your Infrastructure Affected by CVE-2019-0708?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.