RCE in widely used Microsoft SQL Server (2014/2016/2017) with high CVSS and CISA KEV listing; active exploitation risk that can disrupt enterprise services.
CVE-2019-1068
Remote code execution in Microsoft SQL Server allowing arbitrary code execution.
Is CVE-2019-1068 being exploited?
Yes. CVE-2019-1068 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2019-1068?
CVE-2019-1068 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2019-1068?
Yes. A fix has been recorded for CVE-2019-1068. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2019-1068 affect?
CVE-2019-1068 affects Microsoft SQL Server 2014, Microsoft SQL Server 2016, Microsoft SQL Server 2017. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2019-1068?
Apply Microsoft security update immediately; isolate internet-exposed servers and follow CISA guidance.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution as the SQL Server Database Engine service account; attackers can run arbitrary code, deploy malware, exfiltrate data, or pivot.
Immediate action required
- affected2014 Service Pack 2 for 32-bit Systems (CU)
- affected2014 Service Pack 2 for x64-based Systems (CU)
- affected2016 for x64-based Systems Service Pack 1 (CU)
- affected2017 for x64-based Systems (CU)
- affected2016 for x64-based Systems Service Pack 2 (CU)
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.