Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2019-1068: Microsoft SQL Server Internal Function Processing Remote Code Execution

Published Jul 15, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS57.3%99th percentile
CISA KEVYesAdded Aug 26, 2026
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2019-1068CWE-20 · Improper Input Validation

CVE-2019-1068 is a remote code execution vulnerability in Microsoft SQL Server caused by incorrect processing of internal functions by the database engine. An authenticated attacker can submit a specially crafted query to execute arbitrary code in the security context of the SQL Server Database Engine service account. Affected releases include SQL Server 2014, 2016, and 2017; SQL Server 2012 is also identified as affected. Exploitation has been reported against unpatched deployments.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits arbitrary code execution with the privileges of the SQL Server Database Engine service account, potentially compromising the database server and exposing data or resources accessible to that account. Highly privileged service-account configurations can expand the impact beyond the database environment to the underlying Windows host.

Mitigation

If you can’t patch tonight, do this now.

Restrict SQL Server access to trusted, authenticated users and networks, reduce external exposure, and segment database systems. Run SQL Server services with least-privilege accounts. Monitor authenticated SQL activity, database audit records, Windows event logs, unexpected process execution, and unusual outbound connections for signs of exploitation or compromise.

Remediation

Patch, then assume compromise.

Apply the applicable Microsoft security updates for CVE-2019-1068, matching the installed SQL Server version, service pack, and cumulative-update or GDR servicing branch. Validate installed builds against Microsoft's remediation guidance and test updates before production deployment. Investigate potentially exposed systems for prior compromise alongside patching; applying an update does not remove an existing attacker foothold. Discontinue affected deployments if patches or mitigations are unavailable.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationSql Serverapplication
Microsoft CorporationSql Server 2016application
Microsoft CorporationSql Server 2017application
FAQ

Frequently asked questions

Is CVE-2019-1068 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Aug 26, 2026.
Is there a public exploit for CVE-2019-1068?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2019-1068, the earliest disclosed Feb 4, 2021.
Is there a patch for CVE-2019-1068?
Apply the applicable Microsoft security updates for CVE-2019-1068, matching the installed SQL Server version, service pack, and cumulative-update or GDR servicing branch. Validate installed builds against Microsoft's remediation guidance and test updates before production deployment.
What products are affected by CVE-2019-1068?
Microsoft Corporation Sql Server, Microsoft Corporation Sql Server 2016, and Microsoft Corporation Sql Server 2017.
How severe is CVE-2019-1068?
CVE-2019-1068 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 57.3% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

32 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+7 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware6Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity21Community discussion across Reddit, Mastodon, and other social sources.