Quick answer
Yes. CVE-2019-1068 in Microsoft SQL Server is being exploited by attackers: CISA added it to its Known Exploited Vulnerabilities catalogue on 26 August 2026. If you run SQL Server, apply the vendor's fix now and check for signs of compromise.
What is CVE-2019-1068?
Microsoft SQL Server Remote Code Execution Vulnerability. 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.
Description from the CISA Known Exploited Vulnerabilities catalogue.
Why it matters
Core server software such as SSH, DNS and print management runs on many machines and often goes unpatched because it is assumed to be stable. Exploited flaws can give attackers remote access, privilege escalation or a way to move between systems.
Higher than 99% of all scored vulnerabilities.
Am I affected? How to check | What to do now |
|---|---|
1Use your vulnerability scanner or package inventory to find every server running the affected software. | 1Apply the fixed package or firmware update. |
2Check versions against the advisory, including appliances that embed the software. | 2Restrict network access to the affected service where it is not needed. |
3Prioritise servers reachable from the internet, then those holding sensitive data. | 3Review authentication and system logs for signs of exploitation. |
Am I affected? How to check
- 1Use your vulnerability scanner or package inventory to find every server running the affected software.
- 2Check versions against the advisory, including appliances that embed the software.
- 3Prioritise servers reachable from the internet, then those holding sensitive data.
What to do now
- 1Apply the fixed package or firmware update.
- 2Restrict network access to the affected service where it is not needed.
- 3Review authentication and system logs for signs of exploitation.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.
How fast to patch
Under the Essential Eight, patches for internet-facing services should be applied within 48 hours when a working exploit exists, and higher maturity levels apply the same 48-hour target to applications such as browsers and office software. A vulnerability in this catalogue has, by definition, been exploited in the wild, so treat it as the 48-hour case.
In the news
- Microsoft testing Remote Lock for lost or stolen Windows devicesBleepingComputer · 17 November 2026
- High volume phishing campaign uses Microsoft 365 outage lures to target multiple industry sectorsMicrosoft Security Blog · 17 November 2026
- Microsoft says months-old bug caused global Microsoft 365 outageBleepingComputer · 16 November 2026
- Microsoft says November security updates cause printing issuesBleepingComputer · 13 November 2026
- Top national security adviser warned of Microsoft risks months agoABC News · 13 November 2026
More in the daily briefing.
Common questions
Is CVE-2019-1068 being exploited?
Yes. It is listed in CISA's Known Exploited Vulnerabilities catalogue, which only includes vulnerabilities with confirmed exploitation in the wild. It was added on 26 August 2026.
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 guidance and CISA’s “Forensics Triage Requirements”. 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 the vendor advisory for fixed versions, and if the system was exposed while unpatched, investigate it for signs of compromise.
Is my Microsoft SQL Server affected?
Check your installed version against the vendor advisory linked on this page. If the affected component is reachable from the internet and unpatched, assume it is at risk and act immediately.