Skip to content
Fencer Intel
high 8.8

CVE-2019-1068 kev in the critical feed json

A remote code execution vulnerability exists in Microsoft SQL Server when it incorrectly handles processing of internal functions, aka 'Mic…

published 7y ago modified 2mo ago also EUVD-2019-9650

cvss
8.8
version 3.1, CNA
cisa kev
Exploited
added 2026-08-26
epss
57.3%
EPSS 57.3% chance of exploitation in 30 days, percentile 99%
public exploits
0
none known

Summary

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

Patch / fix

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.

  • microsoft sql_server_2016 13.0.4259.0, 13.0.4604.0, 13.0.5101.9, 13.0.5366.0
  • microsoft sql_server_2017 14.0.2027.2, 14.0.3192.2

Is CVE-2019-1068 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. CISA SSVC: exploitation active
  3. Added to CISA KEV
  4. CISA patch deadline

Known exploited

Added
2mo ago
Patch by
2026-08-29 (2mo ago)
Ransomware
Not known
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.
Vendor, product
Microsoft, SQL Server
CISA name
Microsoft SQL Server Remote Code Execution Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
2mo ago

Exploit prediction

57.27% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected products

  • Microsoft Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (GDR)
  • Microsoft Microsoft SQL Server
  • Microsoft Microsoft SQL Server 2014 Service Pack 2 for x64-based Systems (GDR)
  • Microsoft Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (GDR)
  • Microsoft Microsoft SQL Server 2017 for x64-based Systems (GDR)
  • Microsoft Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR)
  • Microsoft Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR)
  • Microsoft Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU)
  • Microsoft Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR)
  • Microsoft Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU)

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.