# CVE-2019-1068: Microsoft SQL Server Remote Code Execution

> Attackers can execute arbitrary code remotely by exploiting improper handling of internal functions in Microsoft SQL Server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 26 Aug 2026 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2019
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-62pw-5pr4-ghr5

## What is CVE-2019-1068?

CVE-2019-1068 is a high-severity code injection vulnerability in Microsoft Sql Server, published on 15 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-1068?

It affects 3 products.


Products: Microsoft Sql Server, Microsoft Sql Server 2016, Microsoft Sql Server 2017.

## How do I fix CVE-2019-1068?

No fix has been published for CVE-2019-1068 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 29 Aug 2026.

## Is CVE-2019-1068 being exploited?

Yes. Attackers have exploited CVE-2019-1068 in the wild since at least 26 Aug 2026.

Public exploit code:

- Root cause analysis and PoC for a Microsoft SQL Server Stack Overflow Vulnerability by reversing svl.dll. (github_poc): https://github.com/Vulnerability-Playground/CVE-2019-1068

## Other vulnerabilities in Microsoft Sql Server

- [CVE-2020-0618](https://insights.sbomify.com/CVE-2020-0618/): Microsoft SQL Server Reporting Services Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2018-8273](https://insights.sbomify.com/CVE-2018-8273/): Memory corruption in Microsoft SQL Server (critical 9.8)
- [CVE-2008-5416](https://insights.sbomify.com/CVE-2008-5416/): Memory corruption in n/a (critical 9.0)
- [CVE-2023-21705](https://insights.sbomify.com/CVE-2023-21705/): Microsoft SQL Server Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-21713](https://insights.sbomify.com/CVE-2023-21713/): Microsoft SQL Server Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1068 and fix it if it is affected.

What it is: CVE-2019-1068 is a high-severity code injection vulnerability in Microsoft Sql Server, published on 15 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-1068 in the wild since at least 26 Aug 2026.

Affected product: Microsoft Sql Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-1068/ (Markdown: https://insights.sbomify.com/CVE-2019-1068/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1068
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1068
- OSV: https://osv.dev/vulnerability/CVE-2019-1068

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-1068/
Summaries are generated and may contain mistakes; the official description above is the record.