How severe is CVE-2019-1163?

CVE-2019-1163 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2019-1163 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (71st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-1163?

CVE-2019-1163 primarily affects Microsoft Windows 10. In total, 11 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2019-1163?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2019-1163 published?

CVE-2019-1163 was published on 2019-08-14 and last updated on 2026-06-17.

CVE-2019-1163

CVE-2019-1163 is a medium-severity vulnerability in Microsoft Windows 10 with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-354.

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
CVSS v2: 4.3
EPSS exploit prediction: 1% (71st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-354
Affected product: Microsoft Windows 10
Published: 2019-08-14
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2019-1163?: 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.
How severe is CVE-2019-1163?: CVE-2019-1163 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2019-1163 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (71st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-1163?: CVE-2019-1163 primarily affects Microsoft Windows 10. In total, 11 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-1163?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-1163 published?: CVE-2019-1163 was published on 2019-08-14 and last updated on 2026-06-17.

References

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1163

Affected products (11)

cpe:2.3:o:microsoft:windows_10:-:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10:1607:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10:1703:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10:1709:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10:1803:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10:1809:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10:1903:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2016:-:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2016:1803:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2016:1903:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2019:-:*:*:*:*:*:*:*

More vulnerabilities in Microsoft Windows 10

CVE-2020-1467 — Critical (CVSS 10.0): An elevation of privilege vulnerability exists when Windows improperly handles hard links. An attacker who successfully…
CVE-2021-26424 — Critical (CVSS 9.9): Windows TCP/IP Remote Code Execution Vulnerability
CVE-2021-28476 — Critical (CVSS 9.9): Windows Hyper-V Remote Code Execution Vulnerability
CVE-2021-26867 — Critical (CVSS 9.9): Windows Hyper-V Remote Code Execution Vulnerability
CVE-2020-1112 — Critical (CVSS 9.9): An elevation of privilege vulnerability exists when the Windows Background Intelligent Transfer Service (BITS) IIS…
CVE-2019-1384 — Critical (CVSS 9.9): A security feature bypass vulnerability exists where a NETLOGON message is able to obtain the session key and sign…

All CVEs affecting Microsoft Windows 10 →

Other CWE-354 vulnerabilities

CVE-2025-11543 — Critical (CVSS 9.8): Improper Validation of Integrity Check Value vulnerability in Sharp Display Solutions projectors allows a attacker may…
CVE-2024-25678 — Critical (CVSS 9.8): In LiteSpeed QUIC (LSQUIC) Library before 4.0.4, DCID validation is mishandled.
CVE-2023-33668 — Critical (CVSS 9.8): DigiExam up to v14.0.2 lacks integrity checks for native modules, allowing attackers to access PII and takeover…
CVE-2017-15994 — Critical (CVSS 9.8): rsync 3.1.3-development before 2017-10-24 mishandles archaic checksums, which makes it easier for remote attackers to…
CVE-2026-49230 — Critical (CVSS 9.1): Improper Validation of Integrity Check Value vulnerability in Apache APISIX. The jwe-decrypt plugin under default…
CVE-2026-34182 — Critical (CVSS 9.1): Issue Summary: Cryptographic Message Services (CMS) processing fails to perform sufficient input validation on the…

Browse all CWE-354 vulnerabilities →