vciy

CVE-2019-1068

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

A remote code execution vulnerability exists in Microsoft SQL Server when it incorrectly handles processing of internal functions, aka 'Microsoft SQL…

CVE-2019-10684 of 4 sources documented this
81

rank 81 = 40 + 22 + 2 + 7 + 10

rank@v1 · act now

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.52845 · CISA KEV listed  ·  without this subject the record ranks 41

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.8, from NVD  ·  without this subject the record ranks 59

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-08-28  ·  without this subject the record ranks 79

How much of the world it touches

NVD CPE configurations

7 products in the CPE ranges  ·  without this subject the record ranks 74

Someone else already set the date

CISA KEV remediation due date

CISA remediation date held  ·  without this subject the record ranks 71

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.64Mover the next 30 days, if this record is yours
Movement+$537,000on 2026-08-28, the last material move, 7 days before this reading
Basisassumeda published average, not your estate

$2.64M = $4.99M incident cost x 1 exposure x 0.52845 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.52845EPSSKEV · LISTED
Severity8.8 HIGHreceipt
Harmtotal lossreceipt
Exploitationin the wild · KEVreceipt
Defenseunaffected versions publishedreceipt
Movementthreshold crossedreceipt
RISING10Risen from 0.32208 to 0.52845 across 31 observations. arc-rules@v1

Foresight · where to check next

MicrosoftActiveMQ BrokerMicrosoft WindowsMicrosoft 365CVE-2022-47966CVE-2022-294991068

This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running Microsoft SQL Server 2014 Service Pack 2…? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-20 Improper Input Validationreceipt
Published consequencesCWE-20: Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory); Confidentiality: Read Memory, Read Files or Directories…[email protected]
Ransomware campaign useUnknown to CISAreceipt

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchsql server 13.0.4259.0; sql server 13.0.4604.0; sql server 13.0.5101.9; sql server 13.0.5366.0; sql server 14.0.2027.2; sql server 14.0.3192.2receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
CISA remediation statusoverdue since 2026-08-29receipt
CISA forensic triageRequired before remediation. BOD 26-04 directs that forensic triage data be collected before this is fixed, because applying the fix destroys the evidence of whether it was already used against you.receipt
CISA required actionApply 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…receipt
Show full 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.

Published to CISA KEV2599 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Exploited in the wild · CISA KEV listed, 2026-08-26.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2021-02-04receipt
  • RUNG 3Exploited in the wild · CISA KEV listed2026-08-26receipt
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD8.8 HIGHreceipt
Exploit probability0.52845 · top 1% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes45 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft 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)…receipt
Published rangesmicrosoft sql server 2014; microsoft sql server 2016 >= 13.0.4001.0 < 13.0.4259.0; microsoft sql server 2016 >= 13.0.4411.0 < 13.0.4604.0; microsoft sql server 2016 >= 13.0.5026.0 < 13.0.5101.9receipt
Show all 7 published ranges
microsoft sql server 2014
microsoft sql server 2016 >= 13.0.4001.0 < 13.0.4259.0
microsoft sql server 2016 >= 13.0.4411.0 < 13.0.4604.0
microsoft sql server 2016 >= 13.0.5026.0 < 13.0.5101.9
microsoft sql server 2016 >= 13.0.5149.0 < 13.0.5366.0
microsoft sql server 2017 >= 14.0.1000.169 < 14.0.2027.2
microsoft sql server 2017 >= 14.0.3006.16 < 14.0.3192.2

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

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

NVD's analysis a second authority

severity
8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-20
affected versions
microsoft sql server 2014; microsoft sql server 2016 >= 13.0.4001.0 < 13.0.4259.0; microsoft sql server 2016 >= 13.0.4411.0 < 13.0.4604.0; and 4 more, listed in full below
also scored by
8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

check it yourself portal.msrc.microsoft.com receipt

Dated events

2022-02-04EPSS moved 0.32 to 0.102025-03-17EPSS moved 0.03 to 0.492026-08-26Added to CISA KEV2026-08-28EPSS moved 0.42 to 0.532026-08-29CISA remediation due

Movement the material steps

14 Apr 20210.32208
4 Feb 20220.09891 · crossed 0.10
23 Jun 20220.10205 · crossed 0.10
7 Mar 20230.01266 · crossed 0.10 · scoring model v2023.03.01
17 Mar 20250.49248 · crossed 0.10 · scoring model v2025.03.14
18 Nov 20250.38586
15 Jun 20260.44665 · scoring model v2026.06.15
24 Jul 20260.33015
28 Aug 20260.52845 · crossed 0.50
Show all 31 observations
14 Apr 20210.32208
4 Feb 20220.09891
8 Mar 20220.09573
23 Jun 20220.10205
9 Jan 20230.10913
7 Mar 20230.01266
1 Apr 20230.01785
4 May 20230.01771
24 Aug 20230.02204
23 Oct 20240.02343
17 Dec 20240.03168
26 Dec 20240.02513
3 Mar 20250.02652
17 Mar 20250.49248
19 Mar 20250.49203
20 Mar 20250.49248
27 Mar 20250.49203
28 Mar 20250.42689
29 Mar 20250.49203
30 Mar 20250.42689
15 Jun 20250.44897
18 Jun 20250.42689
23 Jun 20250.44538
6 Jul 20250.42689
19 Oct 20250.41568
18 Nov 20250.38586
21 Nov 20250.41568
15 Jun 20260.44665
24 Jul 20260.33015
23 Aug 20260.42088
28 Aug 20260.52845

31 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.52845Published2019-07-15Public PoC2021-02-04CISA KEV2026-08-26Index as of2026-09-04

Listed by CISA 2599 days after it published and the record had been public for 7 years, 1 month when this index was last written.

Published 2019-07-15 receipt · Public PoC 2021-02-04 receipt · CISA KEV 2026-08-26 receipt · Index as of 2026-09-04 derived

The pattern, elsewhere

This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2019-0604 · Microsoft SharePoint Servermatches 8 of 9KEV listed · 2019receipt
CVE-2026-34197 · Apache ActiveMQ Brokermatches 8 of 9KEV listed · 2026receipt
CVE-2025-32706 · Microsoft Windows 10 Version 1507matches 8 of 9KEV listed · 2025receipt
CVE-2024-21413 · Microsoft 365 Apps for Enterprisematches 8 of 9KEV listed · 2024receipt
CVE-2022-47966matches 7 of 8KEV listed · 2023receipt
CVE-2022-29499matches 7 of 8KEV listed · 2022receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

13347 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2019-1068.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.