Verified reference description
The following technical description is credited to the CISA KEV dataset (CC0):
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.
Record and timeline
- Product: Microsoft — SQL Server
- Identifier: CVE-2019-1068
- CVE record published: 2019-07-15
- Added to CISA KEV: 2026-08-26
- Reference score: 8.8/10, CVSS 3.1; provider: CISA-ADP
- Weakness class: Not specified in the KEV entry
A KEV addition date is not a discovery date. CVSS describes technical severity; actual exposure and asset importance also influence remediation priority.
Defensive next steps
Match the installed Microsoft SQL Server version and configuration against the linked technical advisory. Apply the manufacturer-approved fixed release or an explicitly documented mitigation; this profile does not guess a fixed version. Verify the patch and review relevant logs afterward. Plan a supported replacement where the product is end-of-life.
Scope and limitations
This is an awareness and defensive-prioritization profile, not a penetration test or a finding that your network is compromised. KEV membership indicates evidence of real-world exploitation. Mandatory CISA deadlines apply to entities covered by the relevant directive, not universally to every reader.
Reported versions and platforms
The table shows up to ten structured version entries from the official CVE-2019-1068 record. Original field names and values are retained deliberately. This is not an automated exposure verdict or a complete list of every product branch; use the full record and vendor advisory for a deployment decision.
| Product in record | Platform | Version fields — original values | Record status |
|---|---|---|---|
| Microsoft — Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (GDR) | — | version=unspecified | affected |
| Microsoft — Microsoft SQL Server | — | version=2014 Service Pack 2 for 32-bit Systems (CU) | affected |
| Microsoft — Microsoft SQL Server | — | version=2014 Service Pack 2 for x64-based Systems (CU) | affected |
| Microsoft — Microsoft SQL Server | — | version=2016 for x64-based Systems Service Pack 1 (CU) | affected |
| Microsoft — Microsoft SQL Server | — | version=2017 for x64-based Systems (CU) | affected |
| Microsoft — Microsoft SQL Server | — | version=2016 for x64-based Systems Service Pack 2 (CU) | affected |
| Microsoft — Microsoft SQL Server 2014 Service Pack 2 for x64-based Systems (GDR) | — | version=unspecified | affected |
| Microsoft — Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (GDR) | — | version=unspecified | affected |
| Microsoft — Microsoft SQL Server 2017 for x64-based Systems (GDR) | — | version=unspecified | affected |
| Microsoft — Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR) | — | version=unspecified | affected |
Full record and technical references
Turn the record into an operational decision
For Microsoft SQL Server, record the asset, effective version, enabled feature and access path. When the reference does not map clearly to your package or branch, retain an explicit unknown status and assign follow-up rather than guessing that the system is safe.
After remediation, record the effective running version, health-check outcome and change time, not merely installation success. Evidence of compromise requires the appropriate incident-response workflow; this page does not diagnose any network as compromised or clean.
Scoring vector and scope
Vector recorded by the reference: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS is owned by FIRST and used by permission. The reference score is not a substitute for organizational risk assessment. Version data comes from the record retrieved for this review and may change when sources are updated.
