CVE-2017-20190

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

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

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%
EPSS %ILE
18%
KEV
Not listed

Published

March 27, 2024

Last Modified

April 15, 2026

References (6)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 20× 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 136 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2017-20190?
CVE-2017-20190 is a publicly disclosed vulnerability 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 CVE-2017-20190 disclosed?
CVE-2017-20190 was first published in the National Vulnerability Database on March 27, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-20190 actively exploited?
CVE-2017-20190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.7% of all scored CVEs.
How do I remediate CVE-2017-20190?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-20190, 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-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.

Start Free Scan →Browse All CVEs