CVE-2017-20190

UNRATEDCVSS · not yet scored

Also known asEUVD-2017-11182 (ENISA EUVD) · GHSA-6399-j99h-665c (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS v2: —Exploit: None knownExposed services: Not assessed

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

CISA-ADP, in the CVE record, lists microsoft windows versions 8 up to and including 11 as affected. No release containing a fix is confirmed on record.

Some Microsoft technologies as used in Windows 8 through 11 allow a temporary client-side performance degradation during processing of multiple Unicode combining characters, aka a "Zalgo text" attack. NOTE: third parties dispute whether the computational cost of interpreting Unicode data should be considered a vulnerability.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

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

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

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

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

Published

March 27, 2024

Last Modified

April 15, 2026

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 92 of 172 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 80 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-11-01 16:28 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-10-31 16:27 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  4. 2026-10-30 16:27 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-10-29 16:27 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-10-28 16:27 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-10-27 16:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-10-26 16:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-10-25 19:35 UTCEG score recompute
  10. 2026-10-25 16:27 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-25 08:58 UTCEG score recompute
  12. 2026-10-25 08:58 UTCGHSA enrichmentGHSA-6399-j99h-665c
  13. 2026-10-24 16:27 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-10-23 16:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-10-22 16:27 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-10-21 16:27 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-10-20 16:27 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-10-19 16:26 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-10-18 16:27 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  20. 2026-10-18 10:33 UTCEG score recompute
  21. 2026-10-17 16:27 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  22. 2026-10-16 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  23. 2026-10-15 16:26 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  24. 2026-10-14 16:27 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  25. 2026-10-13 16:27 UTCEPSS rescoreEPSS 0.3% · 16th percentile
Show 67 more
  1. 2026-10-12 20:30 UTCEG score recompute
  2. 2026-10-12 16:28 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  3. 2026-10-12 00:53 UTCEG score recompute
  4. 2026-10-11 13:41 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  5. 2026-10-10 19:55 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  6. 2026-10-09 20:02 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  7. 2026-10-08 16:36 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  8. 2026-10-07 23:41 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  9. 2026-10-06 15:12 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  10. 2026-10-05 17:38 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-04 23:18 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-03 14:21 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-09-30 14:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-09-30 09:32 UTCEG score recompute
  15. 2026-09-28 13:45 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-09-27 13:40 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-09-26 15:53 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-09-24 13:59 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  19. 2026-09-18 19:22 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-09-17 19:22 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-09-15 03:05 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-09-13 16:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-09-12 14:55 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-09-11 09:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-09-07 15:56 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-09-06 13:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  27. 2026-09-05 15:23 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  28. 2026-09-04 13:56 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  29. 2026-09-02 14:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  30. 2026-09-01 03:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  31. 2026-08-30 19:13 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  32. 2026-08-27 14:21 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-08-26 14:41 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  34. 2026-08-25 13:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  35. 2026-08-21 23:44 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  36. 2026-08-20 22:51 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  37. 2026-08-19 16:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  38. 2026-08-18 13:43 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  39. 2026-08-17 13:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  40. 2026-08-16 14:51 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  41. 2026-08-16 02:10 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  42. 2026-08-15 01:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  43. 2026-08-12 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  44. 2026-08-09 13:42 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-08-07 16:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  46. 2026-08-06 13:42 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  47. 2026-08-05 19:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  48. 2026-08-04 15:05 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-08-01 04:11 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  50. 2026-07-30 16:24 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  51. 2026-07-30 01:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  52. 2026-07-28 15:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-07-26 14:51 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  54. 2026-07-23 14:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-07-23 01:28 UTCEG score recompute
  56. 2026-07-22 22:08 UTCEG score recompute
  57. 2026-07-22 14:04 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  58. 2026-07-20 17:04 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  59. 2026-07-19 14:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  60. 2026-07-19 02:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  61. 2026-07-18 10:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  62. 2026-07-16 16:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-07-15 16:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  64. 2026-07-15 01:56 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  65. 2026-07-13 22:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  66. 2026-07-12 05:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  67. 2026-07-11 08:24 UTCEPSS rescoreEPSS 0.3% · 17th percentile

Frequently asked(4)

What is CVE-2017-20190?
CVE-2017-20190 is a vulnerability whose severity is not yet rated; its CVE record was published on March 27, 2024. Some Microsoft technologies as used in Windows 8 through 11 allow a temporary client-side performance degradation during processing of multiple Unicode combining characters, aka a "Zalgo text" attack. NOTE: third parties dispute whether the computational cost of interpreting Unicode data should be…
When was the CVE record for CVE-2017-20190 published?
The CVE record for CVE-2017-20190 was published on March 27, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2017-20190 actively exploited?
CVE-2017-20190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
How do I remediate CVE-2017-20190?
No fix for CVE-2017-20190 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. CISA-ADP, in the CVE record, lists microsoft windows versions 8 up to and including 11 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-20190?

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