CVEs / CVE-2019-1068
CVE-2019-1068: Microsoft SQL Server Remote Code Execution Vulnerability
- Known exploited in the CISA KEV catalog since 26 Aug 2026
- high 8.8 CVSS 3.1 (NVD)
- EPSS 57.2% chance of exploitation in the next 30 days, higher than 99% of CVEs (30 Oct 2026)
- Last changed at its sources
Are you affected? Check your servers with Stackurity: it lists the software on each server and the vulnerabilities to fix first.
Check your servers with Stackurity Already using Stackurity? Search for CVE-2019-1068
Summary
Microsoft SQL Server contains a remote code execution vulnerability that could allow an attacker to execute code in the context of the SQL Server Database Engine service account.
Description
A remote code execution vulnerability exists in Microsoft SQL Server when it incorrectly handles processing of internal functions, aka 'Microsoft SQL Server Remote Code Execution Vulnerability'.
Affected and fixed versions
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (GDR) | unspecified | — |
| Microsoft Microsoft SQL Server | 2014 Service Pack 2 for 32-bit Systems (CU) | — |
| Microsoft Microsoft SQL Server | 2014 Service Pack 2 for x64-based Systems (CU) | — |
| Microsoft Microsoft SQL Server | 2016 for x64-based Systems Service Pack 1 (CU) | — |
| Microsoft Microsoft SQL Server | 2017 for x64-based Systems (CU) | — |
| Microsoft Microsoft SQL Server | 2016 for x64-based Systems Service Pack 2 (CU) | — |
| Microsoft Microsoft SQL Server 2014 Service Pack 2 for x64-based Systems (GDR) | unspecified | — |
| Microsoft Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (GDR) | unspecified | — |
| Microsoft Microsoft SQL Server 2017 for x64-based Systems (GDR) | unspecified | — |
| Microsoft Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR) | unspecified | — |
| Microsoft Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR) | unspecified | — |
| Microsoft Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU) | unspecified | — |
| Microsoft Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR) | unspecified | — |
| Microsoft Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU) | unspecified | — |
Exploitation
| In CISA KEV since | 26 Aug 2026 |
|---|---|
| Due date for US federal agencies | 29 Aug 2026 |
| Used in ransomware campaigns | Unknown |
| Required action | Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. |
Severity
| CVSS 3.1 | 8.8 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HScored by NVD |
|---|---|
| Weakness | CWE-20 |
References
- CVE-2019-1068 on NVD
- CVE-2019-1068 in the CISA KEV catalog
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1068 (cited by CISA)
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (cited by CISA)
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk (cited by CISA)
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1068 Patch, Vendor Advisory
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1068 US Government Resource
Sources
Exploitation status from the CISA Known Exploited Vulnerabilities catalog. EPSS scores from FIRST. Descriptions, severity and references from the National Vulnerability Database. Open-source package versions from OSV (CC-BY 4.0). Text is shown as each source states it; Stackurity does not edit it. Check the vendor's advisory before acting.
This product uses data from the NVD API but is not endorsed or certified by the NVD.