CVE-2017-20190
Some Microsoft technologies as used in Windows 8 through 11 allow a temporary client-side...
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.
Exploit likelihood
What each source reports
CVE List No score
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.
- Record
CVE-2017-20190- Weakness
- CWE-176
- Updated
- 2026-11-02
EUVDEUVD-2017-11182 No score
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.
- Record
EUVD-2017-11182- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-6399-j99h-665c No score
Some Microsoft technologies as used in Windows 8 through 11 allow a temporary client-side...
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.
- Record
GHSA-6399-j99h-665c- Weakness
- CWE-176
- Updated
- 2026-11-02
NVD No score
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.
- Record
CVE-2017-20190- Weakness
- CWE-176
- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2017-20190 is a vulnerability with no CVSS score yet in Microsoft Windows, published March 26, 2024. Its validity is disputed. EPSS puts the chance of exploitation in the next 30 days at 0.26%, the 18th percentile.