CVE-2019-1068: Microsoft SQL Server Remote Code Execution
Microsoft SQL Server · listed in the CISA catalog of actively exploited vulnerabilities since 2026-08-26.
- CVSS v3.1 (CISA ADP)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 57%
- higher than 99% of all CVEs
- Added to CISA KEV
- 2026-08-26
- US federal due date 2026-08-29
- Automatable (CISA SSVC)
- no
- technical impact: total
What is CVE-2019-1068?
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'.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (GDR)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft SQL ServerAffectedFixed in
- 2014 Service Pack 2 for 32-bit Systems (CU)
- 2014 Service Pack 2 for x64-based Systems (CU)
- 2016 for x64-based Systems Service Pack 1 (CU)
- 2016 for x64-based Systems Service Pack 2 (CU)
- 2017 for x64-based Systems (CU)
not stated - Microsoft SQL Server 2014 Service Pack 2 for x64-based Systems (GDR)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (GDR)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft SQL Server 2017 for x64-based Systems (GDR)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (GDR)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft SQL Server |
| not stated |
| Microsoft SQL Server 2014 Service Pack 2 for x64-based Systems (GDR)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (GDR)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft SQL Server 2017 for x64-based Systems (GDR)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU)Affected versions are not specified in the CVE record. | – | not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
- CISA's deadline for US federal agencies: 2026-08-29 (passed) – a useful benchmark for everyone else, too.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-20 Improper Input Validation
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.