Microsoft SQL Server: attackers can run their own code
OFFICIAL NAME: Microsoft SQL Server Remote Code Execution Vulnerability
WHAT IT IS · SERVERS AND BACKUPSIt runs or protects many systems at once, including your backups.
DO THIS FIRSTPatch it and keep its admin access off the internet. Not sure if you use it? Send this page to your IT provider or security lead and ask.
TECHNICAL SUMMARY 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.
WHY THIS VERDICT Attacks are confirmed. The exploit prediction score is 57%.
- HIGHEST CONFIRMED RUNG
- EXPLOITED
- CISA KEV
- LISTED
- EXPLOIT CODE
- NONE KNOWN
How far has it climbed?
01 TALK
□ NO EVIDENCE YETNEWEST EVIDENCE NONE YETNo evidence yet.
SRC: NONE YET02 EXPOSED
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETWe have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.
03 TRIED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESAttacks that worked are confirmed (step 4), so attempts count as confirmed too.
04 EXPLOITED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESMicrosoft 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. CISA Vulnrichment marks CVE-2019-1068 as actively exploited.
05 DAMAGE
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETBreach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.
When each thing happened
- DISCLOSED
- EXPLOIT CODE PUBLICNOT YET
- FIRST ATTACK REPORT
- CISA KEV LISTING
- US FEDERAL DEADLINE
THE FIX
CISA's instruction: apply the vendor's fix, or stop using the product if no fix exists. The deadline CISA set for US federal agencies, Aug 29, 2026, has passed. It is a US government deadline; use it as a guide.
Questions to ask this week
- Do we run Microsoft SQL Server? If yes, is it patched or cut off from the internet?
- Who owns fixing it, and by what date?
- Have we checked for signs of attack since the first report, not just since the patch?
How it unfolded
- Attack activity. JUL 15, 2019CISA Vulnrichment marks CVE-2019-1068 as actively exploited
- Attack activity. AUG 25, 2026Microsoft SQL Server Remote Code Execution Vulnerability