CVE-2017-8759

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

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. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2017-17705 (ENISA EUVD) · GHSA-rc4w-p9f6-7c7q (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 89%CVSS: 7.8Exploit: Public PoCExposed 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
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
89% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2017-8759

Published

September 13, 2017

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Nov 9, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: microsoft.
Web page

GitHub - GitHubAssessments/CVE_Assessments_01_2020 · GitHub

https://github.com/GitHubAssessments/CVE_Assessments_01_2020
Web page🟡 PoC Available

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

https://www.exploit-db.com/exploits/42711/
Microsoft

Security Update Guide - Microsoft Security Response Center

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8759
Web page

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
Web page

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
Web page

PSIRT.COM — Product Security Incident Response Team

http://www.securityfocus.com/bid/100742

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 0× in last 7d / 0× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 00:25 UTCEchelonGraph re-scored
  2. 2026-11-13 00:25 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-11-12 01:25 UTCEchelonGraph re-scored
  4. 2026-11-12 01:25 UTCVendor advisory
  5. 2026-11-12 01:25 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-11-11 16:29 UTCEPSS rescoreEPSS 89% · 99th percentile
  7. 2026-11-11 02:25 UTCEchelonGraph re-scored
  8. 2026-11-11 02:25 UTCVendor advisory
  9. 2026-11-11 02:25 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-11-10 16:31 UTCEPSS rescoreEPSS 89% · 99th percentile
  11. 2026-11-10 03:23 UTCEchelonGraph re-scored
  12. 2026-11-10 03:23 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-11-09 04:22 UTCEchelonGraph re-scored
  14. 2026-11-09 04:22 UTCVendor advisory
  15. 2026-11-09 04:22 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-11-08 05:21 UTCEchelonGraph re-scored
  17. 2026-11-08 05:21 UTCVendor advisory
  18. 2026-11-08 05:21 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-11-07 06:20 UTCEchelonGraph re-scored
  20. 2026-11-07 06:20 UTCVendor advisory
  21. 2026-11-07 06:20 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-11-06 07:20 UTCEchelonGraph re-scored
  23. 2026-11-06 07:20 UTCVendor advisory
  24. 2026-11-06 07:20 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-11-05 08:20 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-05 08:20 UTCVendor advisory
  2. 2026-11-05 08:20 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-11-04 16:28 UTCEPSS rescoreEPSS 89% · 99th percentile
  4. 2026-11-04 09:20 UTCEchelonGraph re-scored
  5. 2026-11-04 09:20 UTCVendor advisory
  6. 2026-11-04 09:20 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-11-03 10:19 UTCEchelonGraph re-scored
  8. 2026-11-03 10:18 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-11-02 11:14 UTCEchelonGraph re-scored
  10. 2026-11-02 11:14 UTCVendor advisory
  11. 2026-11-02 11:13 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-11-01 16:28 UTCEPSS rescoreEPSS 89% · 99th percentile
  13. 2026-11-01 12:13 UTCEchelonGraph re-scored
  14. 2026-11-01 12:13 UTCVendor advisory
  15. 2026-11-01 12:13 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-31 16:27 UTCEPSS rescoreEPSS 89% · 99th percentile
  17. 2026-10-31 13:12 UTCEchelonGraph re-scored
  18. 2026-10-31 13:12 UTCVendor advisory
  19. 2026-10-31 13:12 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-30 14:09 UTCEchelonGraph re-scored
  21. 2026-10-30 14:09 UTCVendor advisory
  22. 2026-10-30 14:09 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-29 15:10 UTCEchelonGraph re-scored
  24. 2026-10-29 15:10 UTCVendor advisory
  25. 2026-10-29 15:10 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  26. 2026-10-28 16:27 UTCEPSS rescoreEPSS 89% · 99th percentile
  27. 2026-10-28 16:10 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-10-27 17:06 UTCEchelonGraph re-scored
  29. 2026-10-27 17:06 UTCVendor advisory
  30. 2026-10-27 17:06 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  31. 2026-10-26 18:05 UTCEchelonGraph re-scored
  32. 2026-10-26 18:04 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  33. 2026-10-25 19:01 UTCEchelonGraph re-scored
  34. 2026-10-25 19:01 UTCVendor advisory
  35. 2026-10-25 19:01 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  36. 2026-10-25 16:27 UTCEPSS rescoreEPSS 89% · 99th percentile
  37. 2026-10-24 20:00 UTCEchelonGraph re-scored
  38. 2026-10-24 20:00 UTCVendor advisory
  39. 2026-10-24 20:00 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  40. 2026-10-23 21:00 UTCEchelonGraph re-scored
  41. 2026-10-23 21:00 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  42. 2026-10-22 21:59 UTCEchelonGraph re-scored
  43. 2026-10-22 21:59 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-10-21 22:59 UTCEchelonGraph re-scored
  45. 2026-10-21 22:59 UTCVendor advisory
  46. 2026-10-21 22:59 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  47. 2026-10-21 16:27 UTCEPSS rescoreEPSS 89% · 99th percentile
  48. 2026-10-20 23:58 UTCEchelonGraph re-scored
  49. 2026-10-20 23:58 UTCVendor advisory
  50. 2026-10-20 23:58 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  51. 2026-10-20 00:58 UTCEchelonGraph re-scored
  52. 2026-10-20 00:58 UTCVendor advisory
  53. 2026-10-20 00:58 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  54. 2026-10-19 16:26 UTCEPSS rescoreEPSS 89% · 99th percentile
  55. 2026-10-19 01:57 UTCEchelonGraph re-scored
  56. 2026-10-19 01:57 UTCVendor advisory
  57. 2026-10-19 01:56 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  58. 2026-10-18 16:27 UTCEPSS rescoreEPSS 89% · 99th percentile
  59. 2026-10-18 10:26 UTCEchelonGraph re-scored
  60. 2026-10-18 02:55 UTCEchelonGraph re-scored
  61. 2026-10-18 02:55 UTCVendor advisory
  62. 2026-10-18 02:54 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-10-17 16:27 UTCEPSS rescoreEPSS 89% · 99th percentile
  64. 2026-10-17 03:54 UTCEchelonGraph re-scored
  65. 2026-10-17 03:54 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  66. 2026-10-16 04:51 UTCEchelonGraph re-scored
  67. 2026-10-16 04:51 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-10-15 05:48 UTCEchelonGraph re-scored
  69. 2026-10-15 05:48 UTCVendor advisory
  70. 2026-10-15 05:47 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-10-14 16:27 UTCEPSS rescoreEPSS 89% · 99th percentile
  72. 2026-10-14 06:47 UTCEchelonGraph re-scored
  73. 2026-10-14 06:47 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8
  74. 2026-10-13 07:45 UTCVendor advisory
  75. 2026-10-13 07:45 UTCGHSA enrichmentGHSA-rc4w-p9f6-7c7q · GitHub severity HIGH · GitHub CVSS 7.8

Publicly available exploits

(7 references)

Public exploit code is referenced for this CVE (1 Exploit-DB entry, 6 GitHub PoCs). Defenders should treat patch urgency accordingly.

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

    Two versions of CVE-2017-8759 exploits

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

    Simple C# implementation of CVE-2017-8759

    Open source ↗
  • GitHub PoCbhdresh/CVE-2017-8759
    Published 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
    Published Sep 13, 2017

    Microsoft Windows .NET Framework - Remote Code Execution

    Open source ↗
  • GitHub PoCnccgroup/CVE-2017-8759
    Published 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
    Published Sep 13, 2017

    Running CVE-2017-8759 exploit sample.

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

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

    Open source ↗

Frequently asked(6)

What is CVE-2017-8759?
CVE-2017-8759 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2017-8759 was made public on September 12, 2017: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on September 13, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
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.