Microsoft SQL Server vulnerabilities: known CVEs & security history
Microsoft · Database · 109 tracked CVEs · 2 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Microsoft SQL Server release lines — 109 in total, with 2 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Microsoft SQL Server's current status and the safe version to run.
Known Microsoft SQL Server CVEs
Actively-exploited and most-severe first. Showing the top 80 of 109. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2020-0618⚡ exploited | high | 8.8 | 99% | 2020 |
| CVE-2012-1856⚡ exploited | high | 8.8 | 72% | 2012 |
| CVE-2002-1145 | high | 10 | 8% | 2002 |
| CVE-2002-0721 | high | 10 | 46% | 2002 |
| CVE-2009-3126 | high | 9.3 | 23% | 2009 |
| CVE-2009-2528 | high | 9.3 | 20% | 2009 |
| CVE-2009-2504 | high | 9.3 | 21% | 2009 |
| CVE-2009-2503 | high | 9.3 | 22% | 2009 |
| CVE-2009-2501 | high | 9.3 | 27% | 2009 |
| CVE-2009-2500 | high | 9.3 | 23% | 2009 |
| CVE-2008-3015 | high | 9.3 | 39% | 2008 |
| CVE-2008-3014 | high | 9.3 | 37% | 2008 |
| CVE-2008-3013 | high | 9.3 | 52% | 2008 |
| CVE-2008-3012 | high | 9.3 | 31% | 2008 |
| CVE-2007-5348 | high | 9.3 | 53% | 2008 |
| CVE-2008-5416 | high | 9 | 87% | 2008 |
| CVE-2008-0086 | high | 9 | 62% | 2008 |
| CVE-2008-0106 | high | 9 | 35% | 2008 |
| CVE-2008-0107 | high | 9 | 35% | 2008 |
| CVE-2023-38169 | high | 8.8 | 1% | 2023 |
| CVE-2023-21713 | high | 8.8 | 2% | 2023 |
| CVE-2023-21705 | high | 8.8 | 1% | 2023 |
| CVE-2021-1636 | high | 8.8 | 6% | 2021 |
| CVE-2019-1068 | high | 8.8 | 45% | 2019 |
| CVE-2016-7254 | high | 8.8 | 12% | 2016 |
| CVE-2016-7253 | high | 8.8 | 12% | 2016 |
| CVE-2016-7250 | high | 8.8 | 12% | 2016 |
| CVE-2016-7249 | high | 8.8 | 12% | 2016 |
| CVE-2024-0056 | high | 8.7 | 1% | 2024 |
| CVE-2015-1763 | high | 8.5 | 12% | 2015 |
| CVE-2009-2502 | high | 8.1 | 22% | 2009 |
| CVE-2023-36785 | high | 7.8 | 1% | 2023 |
| CVE-2023-36730 | high | 7.8 | 1% | 2023 |
| CVE-2023-36420 | high | 7.8 | 1% | 2023 |
| CVE-2023-36417 | high | 7.8 | 1% | 2023 |
| CVE-2023-32028 | high | 7.8 | 1% | 2023 |
| CVE-2023-32027 | high | 7.8 | 1% | 2023 |
| CVE-2023-32026 | high | 7.8 | 1% | 2023 |
| CVE-2023-32025 | high | 7.8 | 1% | 2023 |
| CVE-2023-29356 | high | 7.8 | 1% | 2023 |
| CVE-2023-29349 | high | 7.8 | 1% | 2023 |
| CVE-2023-21718 | high | 7.8 | 1% | 2023 |
| CVE-2023-21704 | high | 7.8 | 0% | 2023 |
| CVE-2023-21528 | high | 7.8 | 0% | 2023 |
| CVE-2022-23276 | high | 7.8 | 1% | 2022 |
| CVE-2008-4110 | high | 7.6 | 18% | 2008 |
| CVE-2022-29143 | high | 7.5 | 2% | 2022 |
| CVE-2017-8516 | high | 7.5 | 8% | 2017 |
| CVE-2007-5090 | high | 7.5 | 2% | 2007 |
| CVE-2007-4814 | high | 7.5 | 46% | 2007 |
| CVE-2002-1872 | high | 7.5 | 6% | 2002 |
| CVE-2002-1137 | high | 7.5 | 9% | 2002 |
| CVE-2002-1138 | high | 7.5 | 5% | 2002 |
| CVE-2002-0982 | high | 7.5 | 8% | 2002 |
| CVE-2002-1123 | high | 7.5 | 78% | 2002 |
| CVE-2002-0859 | high | 7.5 | 26% | 2002 |
| CVE-2002-0644 | high | 7.5 | 11% | 2002 |
| CVE-2002-0645 | high | 7.5 | 4% | 2002 |
| CVE-2002-0649 | high | 7.5 | 85% | 2002 |
| CVE-2002-0624 | high | 7.5 | 23% | 2002 |
| CVE-2002-0641 | high | 7.5 | 11% | 2002 |
| CVE-2002-0186 | high | 7.5 | 55% | 2002 |
| CVE-2002-0187 | high | 7.5 | 14% | 2002 |
| CVE-2002-0154 | high | 7.5 | 25% | 2002 |
| CVE-2002-0056 | high | 7.5 | 25% | 2002 |
| CVE-2001-0542 | high | 7.5 | 14% | 2001 |
| CVE-2000-0202 | high | 7.5 | 10% | 2000 |
| CVE-2023-23384 | high | 7.3 | 1% | 2023 |
| CVE-2003-0230 | high | 7.2 | 2% | 2003 |
| CVE-2003-0232 | high | 7.2 | 4% | 2003 |
| CVE-2002-0642 | high | 7.2 | 50% | 2002 |
| CVE-2001-0344 | high | 7.2 | 2% | 2001 |
| CVE-2000-0199 | high | 7.2 | 1% | 2000 |
| CVE-1999-1556 | high | 7.2 | 1% | 1998 |
| CVE-2015-1762 | high | 7.1 | 10% | 2015 |
| CVE-2014-4061 | medium | 6.8 | 26% | 2014 |
| CVE-2019-0819 | medium | 6.5 | 5% | 2019 |
| CVE-2016-7252 | medium | 6.5 | 18% | 2016 |
| CVE-2015-1761 | medium | 6.5 | 19% | 2015 |
| CVE-2016-7251 | medium | 6.1 | 8% | 2016 |
29 older / lower-severity CVEs not shown — see Microsoft SQL Server's full record.
Is my Microsoft SQL Server version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Microsoft SQL Server version → · Monitor Microsoft SQL Server for new CVEs →
Microsoft SQL Server vulnerabilities — frequently asked
How many known vulnerabilities does Microsoft SQL Server have?
IsItPatched tracks 109 CVEs for Microsoft SQL Server, 2 of which are actively exploited (CISA KEV). 0 are critical-severity and 75 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Microsoft SQL Server have any actively-exploited vulnerabilities?
Yes — 2 Microsoft SQL Server CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild. Patch these as a priority.
What is the most severe Microsoft SQL Server vulnerability?
Among tracked issues, CVE-2020-0618 (HIGH, CVSS 8.8), which is actively exploited, ranks highest — a Insecure deserialization weakness.
Is Microsoft SQL Server safe to use?
It depends on the version. The latest supported Microsoft SQL Server release (17.0.4045.5 CU5) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Microsoft SQL Server security status · Microsoft SQL Server end-of-life · actively-exploited CVEs. Always verify against Microsoft's advisories — see our disclaimer.