⚠ Known Exploited Vulnerability (KEV) Tracker

Description

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.

Lifecycle Timeline

• 2019-07-09
  Vendor fix published

  Microsoft shipped a fix for SQL Server.

  MSRC →
• 2019-07-15
  CVE published 6 days later

  Entered the public CVE record.

  CVE.org →
• 2021-02-04
  Public exploit code 19 months later

  Public GitHub repository Vulnerability-Playground/CVE-2019-1068 — unvetted, may contain malware

  GitHub PoC →
• 2022-06-25
  EPSS flags exploitation risk 17 months later

  Probability rose past 10%, from 9.6% to 10.2%. Dated to the sampled week.

  FIRST EPSS →
• 2026-08-26
  Added to CISA KEV 4.2 years later

  Listed as known exploited, which starts the federal remediation clock.

  CISA KEV →
• 2026-08-29
  Federal remediation due 3 days later

  Deadline for federal civilian agencies under BOD 22-01 — now passed.

  CISA KEV
• not recorded
  First national advisory

  No tracked government advisory analyses this CVE. Routine KEV catalog-addition alerts do not count here.

Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 262 points from 2021-12-11, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 52.8% on 2026-08-29.

Published Applicability

Check whether a specific version is affected →

What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.

Research & News Coverage

Articles from monitored vendor research blogs and security news feeds that specifically mention this CVE. Coverage begins when feed monitoring started; earlier articles are not indexed.

Detection & Exploitation

Coverage across public collections only: Nuclei and OpenVAS NVT (scan); Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM); Metasploit, Exploit-DB and public GitHub repositories (exploit). Absence here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by PoC-in-GitHub (CC0) and are not vetted: some are fakes and some are malware. Treat them as evidence that code was published, not as code to run.
OpenVAS coverage derives from the Greenbone Community Feed, made available under the Open Database License (ODbL) v1.0; its individual Vulnerability Tests are licensed GNU GPL v2.

Microsoft SQL Server Remote Code Execution Vulnerability

The vendor's own judgement about their own code, shown alongside CISA's rather than merged into it. The exploitability index is a forward-looking prediction, distinct from a CVSS severity or CISA's SSVC decision, and vendors often report observed exploitation before a CVE reaches the KEV catalog. Vendor advisory →

CISA Assessment (Vulnrichment / SSVC)

D3FEND Countermeasures

Defensive techniques inferred by MITRE D3FEND from the underlying weakness (CWE-20) — general hardening and detection guidance for this weakness class, not a vendor patch for this specific CVE.

KEV Catalog Status

Listed By

Referenced in Advisories

Weaponization Timeline — Offensive & Testing Tools

No exploit-tool sightings recorded for this CVE.

Evidence tiers are explained on the About page — a merged Metasploit module is far stronger evidence than a distro package mention.

External References

CVE.org record → NVD entry → CISA KEV catalog → Microsoft MSRC advisory → FortiGuard Labs → Rapid7 AttackerKB →