CVE-2019-1150

Microsoft Graphics Remote Code Execution Vulnerability

HIGH
8.8
CVSS Score
Published: August 14, 2019 at 08:55 PM UTC
Updated: June 17, 2026 at 02:27 AM UTC
17 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1703 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1703 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 26%
SSVC
No known exploit

Description

A remote code execution vulnerability exists when the Windows font library improperly handles specially crafted embedded fonts. An attacker who successfully exploited the vulnerability could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. There are multiple ways an attacker could exploit the vulnerability: In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability and then convince users to view the website. An attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically by getting them to click a link in an email or instant message that takes users to the attacker's website, or by opening an attachment sent through email. In a file-sharing attack scenario, an attacker could provide a specially crafted document file designed to exploit the vulnerability and then convince users to open the document file. The security update addresses the vulnerability by correcting how the Windows font library handles embedded fonts.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.1.0 ≤ v < publication6.1.0sp1
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
6.3.0 ≤ v < publication6.3.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
6.0.0 ≤ v < publication6.1.0 ≤ v < publication6.0.06.1.0r2 sp1sp2
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
6.2.0 ≤ v < publication6.3.0 ≤ v < publication6.2.06.3.0r2
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.018031903
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787CWE-94

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card