CVE-2017-8759

CRITICALNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 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 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 89%CVSS: 7.8Exploit: cisa kev · ssvc active · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

Microsoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7 allow an attacker to execute code remotely via a malicious document or application, aka ".NET Framework Remote Code Execution Vulnerability."

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

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
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
89%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 13, 2017

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated May 19, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft.
generic

GitHub - GitHubAssessments/CVE_Assessments_01_2020 · GitHub

https://github.com/GitHubAssessments/CVE_Assessments_01_2020
generic
http://www.securitytracker.com/id/1039324
generic
http://www.securityfocus.com/bid/100742
generic🟡 PoC Available

Microsoft Windows .NET Framework - Remote Code Execution - Windows remote Exploit

https://www.exploit-db.com/exploits/42711/
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8759
generic🔴 Active Exploitation

GitHub - nccgroup/CVE-2017-8759: NCC Group's analysis and exploitation of CVE-2017-8759 along with further refinements · GitHub

https://github.com/nccgroup/CVE-2017-8759
generic

GitHub - bhdresh/CVE-2017-8759: Exploit toolkit CVE-2017-8759 - v1.0 is a handy python script which provides pentesters and security researchers a quick and effective way to test Microsoft .NET Framework RCE. It could generate a malicious RTF file and deliver metasploit / meterpreter / other payload to victim without any complex configuration. · GitHub

https://github.com/bhdresh/CVE-2017-8759

Vendor Advisories for CVE-2017-8759(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 96× in last 7d / 407× 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 1,670 total refreshes for this CVE.

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

Publicly available exploits

(7 references)

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

  • GitHub PoCashr/CVE-2017-8759-exploits
    First seen Sep 19, 2017

    Two versions of CVE-2017-8759 exploits

    Open source ↗
  • GitHub PoCJonasUliana/CVE-2017-8759
    First seen Sep 17, 2017

    Simple C# implementation of CVE-2017-8759

    Open source ↗
  • GitHub PoCbhdresh/CVE-2017-8759
    First seen Sep 14, 2017

    Exploit toolkit CVE-2017-8759 - v1.0 is a handy python script which provides pentesters and security researchers a quick and effective way to test Microsoft .NET Framework RCE. It could generate a malicious RTF file and deliver metasploit / meterpreter / other payload to victim without any complex configuration.

    Open source ↗
  • Exploit-DBEDB-42711
    First seen Sep 13, 2017

    Microsoft Windows .NET Framework - Remote Code Execution

    Open source ↗
  • GitHub PoCnccgroup/CVE-2017-8759
    First seen Sep 13, 2017

    NCC Group's analysis and exploitation of CVE-2017-8759 along with further refinements

    Open source ↗
  • GitHub PoCVoulnet/CVE-2017-8759-Exploit-sample
    First seen Sep 13, 2017

    Running CVE-2017-8759 exploit sample.

    Open source ↗
  • GitHub PoCvysecurity/CVE-2017-8759
    First seen Sep 13, 2017

    CVE-2017-8759 - A vulnerability in the SOAP WDSL parser.

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2017-8759?
CVE-2017-8759 is a critical vulnerability published on September 13, 2017. Microsoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7 allow an attacker to execute code remotely via a malicious document or application, aka ".NET Framework Remote Code Execution Vulnerability."
When was CVE-2017-8759 disclosed?
CVE-2017-8759 was first published on September 13, 2017, 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-2017-8759 actively exploited?
Yes. CISA added CVE-2017-8759 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft .NET Framework. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2017-8759?
CVE-2017-8759 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2017-8759?
CVE-2017-8759 affects Microsoft .NET Framework.
How do I remediate CVE-2017-8759?
A fix for CVE-2017-8759 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-8759 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-8759

Explore →

Is Your Infrastructure Affected by CVE-2017-8759?

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

Book a Demo →Browse All CVEs