Skip to main content
ExploitedIn CISA KEVFix available

CVE-2019-1068

Exploitation confirmed. First attested on 2026-08-26 by CISA-ADP, CISA KEV, GCVE · previdian.

  • Published2019-07-15
  • Fixed in13.0.5366.0 · 13.0.5101.9 · 13.0.4604.0 · 13.0.4259.0
  • WeaknessCWE-20

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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'.

Timeline

dates in UTC
  1. 2019-07-1519:15CVE publishedNVD
  2. 2026-08-26Added to the CISA KEV catalogCISA KEV
  3. 2026-08-26Listed as exploited by GCVEGCVE
  4. 2026-08-26Exploitation first reportedCISA KEV
  5. 2026-08-2617:44SSVC exploitation set to activeCISA-ADP

Observed activity

isMalicious corpus · updated 2026-11-03 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-1068?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-1068?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Microsoft sql server 2016
BranchAffectedFixed in
13.0≥ 13.0.5149.0, < 13.0.5366.013.0.5366.0
13.0≥ 13.0.5026.0, < 13.0.5101.913.0.5101.9
13.0≥ 13.0.4411.0, < 13.0.4604.013.0.4604.0
13.0≥ 13.0.4001.0, < 13.0.4259.013.0.4259.0
Microsoft sql server 2017
BranchAffectedFixed in
14.0≥ 14.0.3006.16, < 14.0.3192.214.0.3192.2
14.0≥ 14.0.1000.169, < 14.0.2027.214.0.2027.2
Microsoft sql server
BranchAffectedFixed in
2014.x= 2014no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA10 products

As microsoft, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (GDR)
  • Microsoft SQL Server
    Affected
    • = 2014 Service Pack 2 for 32-bit Systems (CU)no fix stated
    • = 2014 Service Pack 2 for x64-based Systems (CU)no fix stated
    • = 2016 for x64-based Systems Service Pack 1 (CU)no fix stated
    • = 2017 for x64-based Systems (CU)no fix stated
    • = 2016 for x64-based Systems Service Pack 2 (CU)no fix stated
  • Microsoft SQL Server 2014 Service Pack 2 for x64-based Systems (GDR)
  • Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (GDR)
  • Microsoft SQL Server 2017 for x64-based Systems (GDR)
  • Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR)

4 more products in the CVE record.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2019-07-15

Fix

  1. Update Microsoft sql server 2016 to 13.0.5366.0 · 13.0.5101.9 · 13.0.4604.0 · 13.0.4259.0
  2. CISA’s 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.due 2026-08-29

Advisories and patches

Detection

read 2026-11-03 22:42 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedVulnerability-Playground/CVE-2019-1068
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

CISA Known Exploited Vulnerability

Date Added
2026-08-26
Patch Due Date
2026-08-29
Ransomware Use
Unknown
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.

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2019-07-15
Last Modified
2026-08-26
NVD status
Analyzed
GitHub Advisory
GHSA-62pw-5pr4-ghr5

Frequently asked questions

What is CVE-2019-1068?

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'.

Is CVE-2019-1068 actively exploited?

Yes. CVE-2019-1068 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2026-08-29.

What is the CVSS score for CVE-2019-1068?

CVE-2019-1068 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, August 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record