Microsoft SQL Server Remote Code Execution Vulnerability (CVE-2019-1068)
Published Last modified In CISA KEV since Sources: CVE.org
What is affected, what to do
An attacker can execute arbitrary code in the context of the SQL Server Database Engine service account via a remote code execution (RCE) vulnerability. This affects specific versions of Microsoft SQL Server 2016 and 2017 as listed. The vulnerability is actively exploited in the wild, as indicated by its inclusion in the CISA KEV catalog. Immediate patching to the latest versions is crucial to mitigate the risk.
The vulnerability is being actively exploited; treat it as a priority. Update sql_server_2016 to version 13.0.5366.0, sql_server_2017 to version 14.0.3192.2. Immediate actions, mitigation and detection rules are in the runbook below.
- Affected
- Microsoft SQL Server
eq 2014 Service Pack 2 for 32-bit Systems (CU)..2014 Service Pack 2 for 32-bit Systems (CU) - Microsoft SQL Server
eq 2014 Service Pack 2 for x64-based Systems (CU)..2014 Service Pack 2 for x64-based Systems (CU) - Microsoft SQL Server
eq 2016 for x64-based Systems Service Pack 1 (CU)..2016 for x64-based Systems Service Pack 1 (CU) - Microsoft SQL Server
eq 2017 for x64-based Systems (CU)..2017 for x64-based Systems (CU) - Microsoft SQL Server
eq 2016 for x64-based Systems Service Pack 2 (CU)..2016 for x64-based Systems Service Pack 2 (CU)
- Microsoft SQL Server
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
8.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
8.8
CVSS v3
Severity High on the scale from 0 to 10.
Source: CVE.org
57.3 %
EPSS score
High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
Source: FIRST EPSS, percentile 99.07
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 222.52 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploited
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 8.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 8.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 57.3 %
- High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 99.07
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- CISA assessment (SSVC)
- Exploitation: active · not automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 26 August 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-20
Response and mitigation
Why act now?
Prioritisation rationale
This flaw is network-reachable with low complexity and needs only a low-privileged database login. Any leaked, guessed, or config-file-embedded SQL credential therefore becomes a path to code execution as the service account, with full impact on confidentiality, integrity, and availability. Exploitation likelihood is rated very high, placing it among the CVEs most likely to be exploited. CISA has not flagged ransomware use, but database servers remain prime targets for data theft, cryptomining, and lateral movement. Treat internet-facing instances, instances broadly reachable from client networks, and those using SQL authentication with a privileged service account as critical and patch them within 24 hours. Tightly segmented internal instances with few, well-managed logins can follow in an expedited regular patch cycle.
Runbook step 1
Immediate response (0-24 h)
- Inventory: Enumerate all SQL Server instances and pull build numbers (
SELECT SERVERPROPERTY('ProductVersion'), SERVERPROPERTY('ProductLevel');). Affected builds per the context include SQL Server 2016 (13.0.4001.0–13.0.4259.0, 13.0.4411.0–13.0.4604.0, 13.0.5026.0–13.0.5101.9, 13.0.5149.0–13.0.5366.0) and SQL Server 2017 (14.0.1000.169–14.0.2027.2, 14.0.3006.16–14.0.3192.2). Other SQL Server versions are also listed, so verify their builds against the vendor advisory. - Patch: Microsoft's security update for CVE-2019-1068 is available. Pick the GDR or CU branch that matches your installed build, and look up exact KB numbers and target builds in the Microsoft Security Update Guide. The target is a build above the upper bound of your affected range. Patch internet-facing and DMZ instances first, then instances with many application or user logins.
- Cut exposure: Immediately block TCP 1433 (or the dynamic ports of named instances) and UDP 1434 (SQL Browser) from the internet and client networks. Allow access only from application servers and admin jump hosts.
- Review logins: Exploitation needs only a low-privileged authenticated session, so list every SQL login and Windows login with connect rights. Disable unused, weak, and shared logins, and rotate passwords for SQL-authentication accounts.
- Compromise assessment: On exposed instances, review child processes of
sqlservr.exeplus logins, jobs, and assemblies created since exposure (see detection). If anything turns up, treat the Database Engine service account as compromised and reset it or migrate it to a gMSA.
- Inventory: Enumerate all SQL Server instances and pull build numbers (
Runbook step 2
Mitigation layers
- Network segmentation: Place database servers in a dedicated VLAN or zone. Inbound, allow only 1433/TCP from named application servers. Block outbound internet access and SMB (445/TCP) towards clients from the DB tier to hamper payload staging and lateral movement.
- Least privilege for the service account: Code runs as the engine service account. Use a virtual service account or gMSA with no local admin or domain rights, and never reuse a service account across servers.
- SQL Server surface reduction: Disable
xp_cmdshell,Ole Automation Procedures,clr enabled, andAd Hoc Distributed Queriesviasp_configureunless strictly required. Minimise membership insysadminanddb_owner, and grants ofCONTROL SERVER. - IAM/authentication: Prefer Windows authentication and turn off mixed mode where feasible. Disable and rename
sa, and require MFA-protected jump hosts for admin access. - Endpoint hardening: Use an EDR, ASR, or WDAC/AppLocker policy to block, or at least alert on,
cmd.exe,powershell.exe,rundll32.exe,certutil.exe, andbitsadmin.exespawned bysqlservr.exe. - IPS: The advisory does not identify a vendor-specific signature. Instead, alert on or drop TDS traffic (1433/TCP) from unexpected source networks via Suricata or firewall policy.
Runbook step 3
Detection rules
- Process ancestry (Sysmon EID 1 / Security 4688): Look for shells, LOLBins, or script hosts spawned by
sqlservr.exe. KQL:DeviceProcessEvents | where InitiatingProcessFileName =~ "sqlservr.exe" and FileName in~ ("cmd.exe","powershell.exe","pwsh.exe","rundll32.exe","certutil.exe","bitsadmin.exe","mshta.exe") - File/network (Sysmon EID 11 / EID 3): Flag
sqlservr.exewriting executables (.exe,.dll,.ps1) outside data and log directories, or opening outbound connections to external IPs. Sigma shape:Image|endswith: '\sqlservr.exe'withTargetFilename|endswith: ['.exe','.dll','.ps1']. - SQL Server audit / Application log: Watch for event 15457 (configuration change, e.g.
xp_cmdshellenabled) and event 33205 (SQL Audit) showingCREATE ASSEMBLY,sp_configure,CREATE LOGIN, orALTER SERVER ROLE. Bursts of event 18456 (failed logins) point to credential brute-forcing ahead of exploitation. - New persistence: Check for new SQL Agent jobs (
msdb.dbo.sysjobs,date_createdcolumn) with CmdExec or PowerShell steps, new services (System 7045), or scheduled tasks (Security 4698) on DB hosts. - Network telemetry (Zeek/Suricata): Flag TDS sessions on 1433/TCP from sources outside the application-server allowlist, especially from client VLANs or the internet.
- Process ancestry (Sysmon EID 1 / Security 4688): Look for shells, LOLBins, or script hosts spawned by
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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'.
Source: CISA KEV Catalog, cvelistv5, NVD (NIST)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Microsoft | Microsoft SQL Server |
|
|
| microsoft | sql_server |
|
|
| microsoft | sql_server_2016 |
|
|
| microsoft | sql_server_2017 |
|
|
Vendors and products
Weakness classes (CWE)
CWE-20Improper Input Validation
Class
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Entry at MITRE CWE-20
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited |
References & sources
- portal.msrc.microsoft.comen-US/security-guidance/advisory/CVE-2019-1068x_refsource_MISC
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1068government-resource
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
NVD analysis modifiedNVD
Product mapping changed:- Microsoft SQL Server (2014-sp2, 2014-sp3)
- Microsoft SQL Server 2016 (13.0.4001.0 – before 13.0.4259.0; 13.0.4411.0 – before 13.0.4604.0; 13.0.5026.0 – before 13.0.5101.9; 13.0.5149.0 – before 13.0.5366.0)
- Microsoft SQL Server 2017 (14.0.1000.169 – before 14.0.2027.2; 14.0.3006.16 – before 14.0.3192.2)
CVSS V3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS V3: before AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, after —
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS removed AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H—Product configuration changed OR *cpe:2.3:a:microsoft:sql_server:2014:sp2:*:*:*:*:*:* *cpe:2.3:a:microsoft:sql_server:2014:sp3:*:*:*:*:*:* *cpe:2.3:a:microsoft:sql_server:2016:sp1:*:*:*:*:x64:* *cpe:2.3:a:microsoft:sql_server:2016:sp2:*:*:*:*:x64:* *cpe:2.3:a:microsoft:sql_server:2017:*:*:*:*:*:x64:*OR *cpe:2.3:a:microsoft:sql_server:2014:sp2:*:*:*:*:*:* *cpe:2.3:a:microsoft:sql_server:2014:sp3:*:*:*:*:*:* *cpe:2.3:a:microsoft:sql_server_2016:*:*:*:*:*:*:*:* versions from (including) 13.0.4001.0 up to (excluding) 13.0.4259.0 *cpe:2.3:a:microsoft:sql_server_2016:*:*:*:*:*:*:*:* versions from (including) 13.0.4411.0 up to (excluding) 13.0.4604.0 *cpe:2.3:a:microsoft:sql_server_2016:*:*:*:*:*:*:*:* versions from (including) 13.0.5026.0 up to (excluding) 13.0.5101.9 *cpe:2.3:a:microsoft:sql_server_2016:*:*:*:*:*:*:*:* versions from (including) 13.0.5149.0 up to (excluding) 13.0.5366.0 *cpe:2.3:a:microsoft:sql_server_2017:*:*:*:*:*:*:*:* versions from (including) 14.0.1000.169 up to (excluding) 14.0.2027.2 *cpe:2.3:a:microsoft:sql_server_2017:*:*:*:*:*:*:*:* versions from (including) 14.0.3006.16 up to (excluding) 14.0.3192.2Reference type added —CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1068 Types: US Government ResourceSource identifier: nvd@nist.gov
CISA KEV entry updated9119a7d8…
4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Date Added added —2026-08-26Due Date added —2026-08-26Required Action added —2026-08-26Vulnerability Name added —2026-08-26Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: active, automatable: no
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1068SSVC assessment changed {"id":"CVE-2019-1068","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-26T15:06:09.622305Z"}{"id":"CVE-2019-1068","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-26T17:44:35.078686Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Record modifiedMicrosoft
Show 3 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1068Reference removed https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1068—Reference type removed https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1068 Types: Patch, Vendor Advisory—Source identifier: secure@microsoft.com
Record modifiedCISA ADP
CVSS V3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA assessment (SSVC): exploitation: none known, automatable: no
Weakness type: CWE-20
Show 3 original changes
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HWeakness type (CWE) added —CWE-20SSVC assessment added —{"id":"CVE-2019-1068","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-26T15:06:09.622305Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Show one older change
Record modifiedCVE Program
Show 3 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1068Reference removed https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1068—Reference type removed https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1068 Types: Patch, Vendor Advisory—Source identifier: af854a3a-2127-422b-91ae-364da2661108
Linked advisories
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2019-1068"><img src="https://intel.neosec.eu/badge/cve/CVE-2019-1068.svg?lang=en" alt="CVE-2019-1068 – NEOSEC Intel" height="20"></a>