1-minute read
What a defender needs to know
CISA added CVE-2019-1068 to its Known Exploited Vulnerabilities catalog on August 26, 2026. The SQL Server flaw was fixed in 2019, but the new exploitation finding makes affected systems a forensic-triage obligation under BOD 26-04. An authenticated attacker with low privileges can submit a crafted query and execute code as the Database Engine service account.
Affected branches are SQL Server 2014 SP2 and SP3, SQL Server 2016 SP1 and SP2, and SQL Server 2017. First fixed builds range from 12.0.5223.6 on the 2014 SP2 GDR line through 14.0.3192.2 on the 2017 CU line. Administrators must match the update to the instance’s existing GDR or CU servicing path and verify every cluster node.
Inventory each instance, host, cluster node, container image, network exposure, build, servicing line, and Database Engine service identity. Preserve volatile and persistent evidence before patching whenever operations allow. The public sources provide no CVE-specific query, process chain, log event, domain, IP address, or hash, so document which SQL, endpoint, authentication, and network records actually cover the exposure window.
Run SERVERPROPERTY('ProductVersion') against every instance and confirm that scanning no longer finds CVE-2019-1068. The verification target is a fixed build everywhere plus a triage report supported by preserved evidence and classified as no evidence of compromise, compromise suspected, or compromise confirmed. A clean version result alone cannot establish that exploitation never occurred before remediation.