vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2019-1163

Windows File Signature Security Feature Bypass Vulnerability

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

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
Start FreeSign In
Severity
MEDIUM5.5
Exploit prediction
EPSS 1%
SSVC
PoC

Description

A security feature bypass exists when Windows incorrectly validates CAB file signatures. An attacker who successfully exploited this vulnerability could inject code into a CAB file without invalidating the file's signature. To exploit the vulnerability, an attacker could modify a signed CAB file and inject malicious code. The attacker could then convince a target user to execute the file. The update addresses the vulnerability by correcting how Windows validates file signatures.

Affected

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

Windows 10· Microsoft
95%
160717031709180318091903
Windows Server 2016· Microsoft
95%
10.0.0 ≤ v < publication10.0.018031903
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 10 1507· Microsoft
60%
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 10 1607· Microsoft
60%
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 10 1703· Microsoft
60%
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 10 1709· Microsoft
60%
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 10 1803· Microsoft
60%
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 10 1809· Microsoft
60%
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 10 1903· Microsoft
60%
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows Server 1803· Microsoft
60%
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:

Patch and advisory references

References (1)

x_refsource_MISCPatchVendor Advisory
Source: [email protected]
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1163

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

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

CVSS

5.5MEDIUMmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-354

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.

Create accountSign in
Free plan, no card