CVE-2019-1068: Microsoft SQL Server Remote Code Execution Vulnerability

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Yes, if you run Microsoft SQL Server. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2026-08-26, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2026-08-29; treat that as the outer limit, not the target.
• EPSS 57.3%, percentile 99: FIRST’s model estimates a 57.3% chance of exploitation activity in the next 30 days, higher than 99% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Needs an account (low (any account)). Exposure depends on who can log in.
• Editorial verdict: Check exposure. SQL Server CVE-2019-1068: 2019 RCE Added to CISA KEV — Any SQL Server 2014, 2016 or 2017 instance updated since July 2019 already has the fix; the real work is finding the instances that never got it, now that CISA says attackers are exploiting the bug, and patching or retiring them.

What it is

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’s summary

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.

Weakness type: CWE-20.

Product: Microsoft SQL Server · Assigned by: microsoft · Published: 2019-07-15

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: low (any account)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: added 2026-08-26; federal due date 2026-08-29. Known ransomware use: Unknown.
• CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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 SSVC assessment: exploitation active, automatable no, technical impact total.
• FIRST EPSS (model of 2026-10-21): 57.27% probability of exploitation activity in the next 30 days; percentile 99.

Timeline

• 2019-07-09 — erroneo.us brief: SQL Server CVE-2019-1068: 2019 RCE Added to CISA KEV
• 2019-07-15 — CVE record published by microsoft
• 2026-08-26 — Added to CISA’s Known Exploited Vulnerabilities catalog
• 2026-08-27 — CVE record last updated
• 2026-08-29 — CISA remediation deadline for US federal agencies

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. Listed in CISA KEV notes (portal.msrc.microsoft.com) portal.msrc.microsoft.com

Vulnerability records

1. CVE.org record CVE-2019-1068 cve.org
2. NVD entry CVE-2019-1068 nvd.nist.gov

Government

1. CISA Known Exploited Vulnerabilities catalog entry cisa.gov
2. Listed in CISA KEV notes (cisa.gov) cisa.gov
3. Listed in CISA KEV notes (cisa.gov) cisa.gov

All exploited Microsoft vulnerabilities · Today’s Security Digest