CVE-2019-0985 json
Microsoft Speech API Remote Code Execution Vulnerability
published 2019-06-12 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-1716
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
A remote code execution vulnerability exists when the Microsoft Speech API (SAPI) improperly handles text-to-speech (TTS) input. The vulnerability could corrupt memory in a way that enables an attacker to execute arbitrary code in the context of the current user. To exploit the vulnerability, an attacker would need to convince a user to open a specially crafted document containing TTS content invoked through a scripting language. The update address the vulnerability by modifying how the system handles objects in memory.
Patch / fix
Exploit prediction
3.52% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C |
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Microsoft Windows 7
- Microsoft Windows 7 Service Pack 1
- Microsoft Windows Server 2008 R2 Systems Service Pack 1
- Microsoft Windows Server 2008 R2 Service Pack 1
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2019-0985
patch, vendor-advisory
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2019-0985
vendor-advisory
Sources
- CVE List CVE-2019-0985
- NVD CVE-2019-0985
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.