What is CVE-2019-1068?

CVE-2019-1068 is Microsoft SQL Server Remote Code Execution Vulnerability. The supplied enrichment data classifies it as Input Validation mapped to CWE-20 Improper Input Validation.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

8 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2019-1068 using CVSS 8.8, EPSS 53%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Dark Caracal (), Bitwise Spider (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighInput Validationpublic exploit

CVE-2019-1068

CVE-2019-1068 — Microsoft SQL Server Remote Code Execution Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2019-1068 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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

Published Jul 15, 2019Updated Aug 27, 2026Sources: NVD, Microsoft (CNA), CISA, FIRST EPSS, Microsoft MSRC, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Aug 26, 2026

EPSS

53%

ahead of 99% of scored CVEs

Affects

Microsoft

28 products listed

CVSS base

8.8

high · 2 sources

Remediation

The vendor's own words where we have them.

Apply Microsoft security update KB4505219 (2019-Jul release) — https://www.microsoft.com/downloads/details.aspx?familyid=e1142d99-3062-4597-bfb4-32a54d3fb2c9.

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.

Federal deadline Aug 29, 2026 — passed 1 day ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Microsoft	Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (GDR)	unspecified	Vulnerable
Microsoft	Microsoft SQL Server	2014 Service Pack 2 for 32-bit Systems (CU)	Vulnerable
Microsoft	Microsoft SQL Server	2014 Service Pack 2 for x64-based Systems (CU)	Vulnerable
Microsoft	Microsoft SQL Server	2016 for x64-based Systems Service Pack 1 (CU)	Vulnerable
Microsoft	Microsoft SQL Server	2017 for x64-based Systems (CU)	Vulnerable
Microsoft	Microsoft SQL Server	2016 for x64-based Systems Service Pack 2 (CU)	Vulnerable
Microsoft	Microsoft SQL Server 2014 Service Pack 2 for x64-based Systems (GDR)	unspecified	Vulnerable
Microsoft	Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (GDR)	unspecified	Vulnerable
Microsoft	Microsoft SQL Server 2017 for x64-based Systems (GDR)	unspecified	Vulnerable
Microsoft	Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR)	unspecified	Vulnerable
Microsoft	Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR)	unspecified	Vulnerable
Microsoft	Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU)	unspecified	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8.8	CVSS 3.1	high	2.8	5.9	NVD, CNA
6.5	CVSS 2.0	medium	8	6.4	NVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Weakness & attack patterns

CWE-20Improper Input Validation

Inferred from the weakness class — not observed against this CVE.

T1562.003Impair Defenses: Impair Command History Logging
T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Aug 26, 2026

Federal deadline

Aug 29, 2026

passed 1 day ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 4 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

3 more posts on this CVEShowing 5 of 8 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (GDR), Microsoft SQL Server, Microsoft SQL Server 2014 Service Pack 2 for x64-based Systems (GDR), Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (GDR), Microsoft SQL Server 2017 for x64-based Systems (GDR), Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR), Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR), Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU), Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR), Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU), Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (CU), Microsoft SQL Server 2017 for x64-based Systems (CU), Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (CU), Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (CU), Microsoft SQL Server 2014 Service Pack 2 for x64-based Systems (CU), Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU 4).
Monitor for scanner or exploit-pattern traffic after 8 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

Dark CaracalBitwise Spider

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 8.8 (AV:N)
Aug 27, 2026 · NVD
Added to CISA KEV catalog
Aug 26, 2026 · CISA
2023
CVE is exploited. "ARPSyndicate/cvemon"
Dec 14, 2023 · SOCRadar CTI
CVE is exploited. "Vulnerability-Playground/CVE-2019-1068"
Dec 14, 2023 · SOCRadar CTI
CVE is exploited. "developer3000S/PoC-in-GitHub"
Dec 14, 2023 · SOCRadar CTI
CVE is exploited. "nomi-sec/PoC-in-GitHub"
Dec 14, 2023 · SOCRadar CTI
2020
Bulletin released on MITRE_REFERENCES.
Sep 16, 2020 · SOCRadar CTI
2019
Initial · CVE published
Jul 15, 2019 · NVD
CVE published by NIST.
Jul 15, 2019 · SOCRadar CTI

Source activity

Readings a source repeats on a schedule, counted rather than listed.

4×Github ReposDec 8, 2019 – Apr 13, 2021 · SOCRadar CTI
3×TweetsAug 27, 2026 – Aug 29, 2026 · SOCRadar CTI
2×ModifiedAug 24, 2020 – Aug 27, 2026 · SOCRadar CTI
2×SvrsAug 27, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Aug 27, 2026 · SOCRadar CTI
1×3 times mentioned on 1 Telegram channelsAug 27, 2026 · SOCRadar CTI

References

15 on the record

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1068
Patch, Vendor Advisory, NIST, MITRE_REFERENCES
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1068
US Government Resource, NIST
www.microsoft.com/downloads/details.aspx?familyid=e1142d99-3062-4597-bfb4-32a54d3fb2c9
Vendor Advisory
www.microsoft.com/downloads/details.aspx?familyid=46ef84af-3af3-4190-849d-d01c4dfe1a85
Vendor Advisory
www.microsoft.com/downloads/details.aspx?familyid=e000ffcd-7e78-4de2-be07-14e5bc10eec2
Vendor Advisory
www.microsoft.com/downloads/details.aspx?familyid=e40888f3-4fe2-4707-808c-594649f1bb0b
Vendor Advisory
www.microsoft.com/downloads/details.aspx?familyid=b422ffe3-1821-4289-9fbc-2693451e3484
Vendor Advisory
www.microsoft.com/downloads/details.aspx?familyid=a1d3acf4-6b55-4b71-96ac-c50f84013be9
Vendor Advisory

Coverage

5 stories from the feeds we poll

Elsewhere on this site

Microsoftevery CVE for this vendor
August 2026what else CISA listed
Input Validationsame class
CWE-20other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2019-1068 is Microsoft SQL Server Remote Code Execution Vulnerability, a high vulnerability affecting Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (GDR), Microsoft SQL Server, Microsoft SQL Server 2014 Service Pack 2 for x64-based Systems (GDR), Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (GDR), Microsoft SQL Server 2017 for x64-based Systems (GDR), Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR), Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR), Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU), Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR), Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU), Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (CU), Microsoft SQL Server 2017 for x64-based Systems (CU), Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (CU), Microsoft SQL Server 2014 Service Pack 2 for 32-bit Systems (CU), Microsoft SQL Server 2014 Service Pack 2 for x64-based Systems (CU), Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU 4) from Microsoft. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 8 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.8 describes technical severity, while EPSS 53% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.