CVE-2019-1068Known exploitationNetwork attack vectorHinoki check available

Authenticated code execution via internal function processing

Published Jul 15, 2019 · Updated Aug 27, 2026

Remote code execution in Microsoft SQL Server 2014, 2016, and 2017 allows remote authenticated users to run code as the Database Engine service. The Database Engine incorrectly processes internal functions supplied through an authenticated database session; Microsoft has not disclosed the specific function or validation failure. A valid low-privilege SQL Server login is required, and successful exploitation runs code with the Database Engine service account's operating-system privileges.

CVSS severity8.8
High
EPSS probability52.84%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Remote code execution in Microsoft SQL Server 2014, 2016, and 2017 allows remote authenticated users to run code as the Database Engine service. The Database Engine incorrectly processes internal functions supplied through an authenticated database session; Microsoft has not disclosed the specific function or validation failure. A valid low-privilege SQL Server login is required, and successful exploitation runs code with the Database Engine service account's operating-system privileges.

The record

CVE
CVE-2019-1068
Published
Jul 15, 2019
Updated
Aug 27, 2026
Vendor
Microsoft
Product
Microsoft SQL Server
Classifications
CWE-20, T1210
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 15, 2019CVE publishedPublication date reported by the CVE source.
  2. Aug 27, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2014 Service Pack 2 for 32-bit Systems (CU)
  2. Affected versionversion=2014 Service Pack 2 for x64-based Systems (CU)
  3. Affected versionversion=2016 for x64-based Systems Service Pack 1 (CU)
  4. Affected versionversion=2016 for x64-based Systems Service Pack 2 (CU)
  5. Affected versionversion=2017 for x64-based Systems (CU)

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Microsoft · Microsoft SQL Serverversion=2014 Service Pack 2 for 32-bit Systems (CU); version=2014 Service Pack 2 for x64-based Systems (CU); version=2016 for x64-based Systems Service Pack 1 (CU); version=2016 for x64-based Systems Service Pack 2 (CU); version=2017 for x64-based Systems (CU)
Microsoft · Microsoft SQL Server 2016version=unspecified
Microsoft · Microsoft SQL Server 2017version=unspecified
Microsoft · Microsoft SQL Server 2014version=unspecified

Published CVSS scores

8.8CISA ADPCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationReported
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-20Improper Input Validation
T1210Exploitation of Remote Services

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Reported exploitation

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo