← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2019-1068 exploited? Yes: in CISA KEV since 26 Aug 2026

Gociux · Microsoft SQL Server · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2019-1068, Microsoft SQL Server Remote Code Execution Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 26 Aug 2026, 2599 days after it was published. It affects Microsoft SQL Server. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 26 Aug 2026
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity8.8CVSS 3.1 · high
US federal due29 Aug 2026BOD 22-01 deadline

What it is

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.

VendorMicrosoft (391 exploited CVEs in KEV)
ProductSQL Server
VulnerabilityMicrosoft SQL Server Remote Code Execution Vulnerability
Weaknessnot specified
Published15 Jul 2019
Added to KEV26 Aug 2026
Reported by (CNA)microsoft

What to do

  1. Check whether you run it. Look for SQL Server in your asset inventory, including appliances and cloud images. Stack check lists every exploited Microsoft CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 15 Jul 2019.
  4. Get told next time. Email alerts when CISA adds a CVE for Microsoft.

Other exploited CVEs in SQL Server

References

Questions

Is CVE-2019-1068 being exploited?

Yes. CISA added CVE-2019-1068 to the Known Exploited Vulnerabilities catalog on 26 Aug 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2019-1068 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2019-1068?

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. Check Microsoft's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected SQL Server and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in August 2026 · Microsoft scorecard · act-now radar.

Running Microsoft in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →