CVE-2019-1057

MS XML Remote Code Execution Vulnerability

HIGH
7.5
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 1903 for 32-bit Systems by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1903 for 32-bit Systems - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 3%
SSVC
No known exploit

Description

A remote code execution vulnerability exists when the Microsoft XML Core Services MSXML parser processes user input. An attacker who successfully exploited the vulnerability could run malicious code remotely to take control of the user’s system. To exploit the vulnerability, an attacker could host a specially crafted website designed to invoke MSXML through a web browser. However, an attacker would have no way to force a user to visit such a website. Instead, an attacker would typically have to convince a user to either click a link in an email message or instant message that would then take the user to the website. When Internet Explorer parses the XML content, an attacker could run malicious code remotely to take control of the user’s system. The update addresses the vulnerability by correcting how the MSXML parser processes user input.

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

7.5HIGHmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-611CWE-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