Vulnerability Database · NuGet · Package report

Microsoft.Data.SqlClient: vulnerability history, versions and safety

Microsoft.Data.SqlClient is a package in the NuGet ecosystem. Vulert records 2 vulnerabilities for it across 29 releases, from Nov 2022 to Jan 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on Microsoft.Data.SqlClient 7.1.1 i

Updated on 23 Oct 2026

Good news: 7.1.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 7.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 7.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 7.1.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 09 Jan 2024 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Stars 996 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by NuGet, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for Microsoft.Data.SqlClient, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
7.1.1 29 Sep 2026 none MIT — Details →
7.1.0 18 Sep 2026 none MIT — Details →
7.0.3 10 Sep 2026 none MIT — Details →
6.1.7 10 Sep 2026 none MIT — Details →
7.1.0-preview3.26238.4 27 Aug 2026 none MIT — Details →
7.1.0-preview2.26190.5 10 Jul 2026 none MIT — Details →
7.1.0-preview2.26190.3 09 Jul 2026 none MIT — Details →
7.0.2 25 Jun 2026 none MIT — Details →
6.1.6 25 Jun 2026 none MIT — Details →
7.1.0-preview1.26124.5 05 May 2026 none MIT — Details →
6.1.5 27 Apr 2026 none MIT — Details →
7.0.1 24 Apr 2026 none MIT — Details →
7.0.0 17 Mar 2026 none MIT — Details →
7.0.0-preview4.26064.3 05 Mar 2026 none MIT — Details →
6.0.5 16 Jan 2026 none MIT — Details →
6.1.4 15 Jan 2026 none MIT — Details →
5.1.9 13 Jan 2026 none MIT — Details →
7.0.0-preview3.25342.7 08 Dec 2025 none MIT — Details →
6.0.4 15 Nov 2025 none MIT — Details →
5.1.8 14 Nov 2025 none MIT — Details →
6.1.3 12 Nov 2025 none MIT — Details →
7.0.0-preview2.25289.6 16 Oct 2025 none MIT — Details →
6.1.2 08 Oct 2025 none MIT — Details →
6.0.3 08 Oct 2025 none MIT — Details →
7.0.0-preview1.25257.1 14 Sep 2025 none MIT — Details →
6.1.1 14 Aug 2025 none MIT — Details →
6.1.0-preview2.25178.5 27 Jun 2025 none MIT — Details →
6.1.0-preview1.25120.4 30 Apr 2025 none MIT — Details →
5.2.3 29 Apr 2025 none MIT — Details →
6.0.2 25 Apr 2025 none MIT — Details →
5.1.7 25 Apr 2025 none MIT — Details →
6.0.1 23 Jan 2025 none MIT — Details →
6.0.0-preview3.24332.3 28 Nov 2024 none MIT — Details →
6.0.0-preview2.24304.8 30 Oct 2024 none MIT — Details →
6.0.0-preview1.24240.8 27 Aug 2024 none MIT — Details →
5.2.2 27 Aug 2024 none MIT — Details →
5.1.6 27 Aug 2024 none MIT — Details →
4.0.6 21 Aug 2024 none MIT — Details →
3.1.7 21 Aug 2024 none MIT — Details →
5.2.1 31 May 2024 none MIT — Details →
5.2.0 28 Feb 2024 none MIT — Details →
5.1.5 29 Jan 2024 none MIT — Details →
5.2.0-preview5.24024.3 25 Jan 2024 none MIT — Details →
5.1.4 09 Jan 2024 none MIT — Details →
5.1.3 09 Jan 2024 none MIT — Details →
4.0.5 09 Jan 2024 none MIT — Details →
3.1.5 09 Jan 2024 none MIT — Details →
2.1.7 09 Jan 2024 none MIT — Details →
5.2.0-preview4.23342.2 08 Dec 2023 none MIT — Details →
3.1.4 31 Oct 2023 none MIT — Details →
4.0.4 30 Oct 2023 none MIT — Details →
5.1.2 26 Oct 2023 none MIT — Details →
5.2.0-preview3.23201.1 20 Jul 2023 none MIT — Details →
5.2.0-preview2.23159.1 08 Jun 2023 none MIT — Details →
2.1.6 27 Apr 2023 H1 MIT Yes Details →
4.0.3 20 Apr 2023 none MIT — Details →
5.2.0-preview1.23109.1 20 Apr 2023 none MIT — Details →
5.0.2 31 Mar 2023 none MIT — Details →
5.1.1 28 Mar 2023 none MIT — Details →
3.1.3 10 Mar 2023 none MIT — Details →
3.1.2 03 Feb 2023 none MIT — Details →
5.1.0 19 Jan 2023 none MIT — Details →
5.1.0-preview2.22314.2 10 Nov 2022 none MIT — Details →
5.0.1 08 Oct 2022 none MIT — Details →
5.1.0-preview1.22279.3 06 Oct 2022 none MIT — Details →
4.1.1 13 Sep 2022 none MIT — Details →
4.0.2 13 Sep 2022 none MIT — Details →
2.1.5 30 Aug 2022 H1 MIT Yes Details →
3.1.1 12 Aug 2022 none MIT — Details →
5.0.0 05 Aug 2022 none MIT — Details →
5.0.0-preview3.22168.1 17 Jun 2022 none MIT — Details →
5.0.0-preview2.22096.2 06 Apr 2022 none MIT — Details →
3.1.0 30 Mar 2022 none MIT — Details →
5.0.0-preview1.22069.1 10 Mar 2022 none MIT — Details →
4.1.0 31 Jan 2022 none MIT — Details →
4.0.1 17 Jan 2022 none MIT — Details →
4.0.0 19 Nov 2021 none MIT — Details →
4.0.0-preview3.21293.2 20 Oct 2021 none MIT — Details →
3.0.1 24 Sep 2021 none MIT — Details →
4.0.0-preview2.21264.2 21 Sep 2021 none MIT — Details →
2.1.4 21 Sep 2021 H1 MIT Yes Details →
4.0.0-preview1.21237.2 25 Aug 2021 none MIT — Details →
3.0.0 09 Jun 2021 none MIT — Details →
2.1.3 21 May 2021 H1 MIT Yes Details →
3.0.0-preview3.21140.5 20 May 2021 none MIT — Details →
3.0.0-preview2.21106.5 16 Apr 2021 none MIT — Details →
3.0.0-preview1.21075.2 16 Mar 2021 none MIT — Details →
1.1.4 10 Mar 2021 H1 MIT Yes Details →
2.1.2 03 Mar 2021 H1 MIT Yes Details →
2.1.1 18 Dec 2020 H1 MIT Yes Details →
2.1.0 19 Nov 2020 H1 MIT Yes Details →
2.1.0-preview2.20297.7 24 Oct 2020 H1 MIT Yes Details →
2.0.1 25 Aug 2020 H1 MIT Yes Details →
2.1.0-preview1.20235.1 22 Aug 2020 H1 MIT Yes Details →
2.0.0 16 Jun 2020 H1 MIT Yes Details →
2.0.0-preview4.20142.4 21 May 2020 H1 MIT Yes Details →
1.1.3 15 May 2020 H1 M1 MIT Yes Details →
2.0.0-preview3.20122.2 01 May 2020 H1 MIT Yes Details →
1.1.2 15 Apr 2020 H1 M1 MIT Yes Details →
2.0.0-preview2.20084.1 24 Mar 2020 H1 MIT Yes Details →
1.1.1 14 Feb 2020 H1 M1 — Yes Details →
2.0.0-preview1.20021.1 21 Jan 2020 H1 — Yes Details →
1.1.0 20 Nov 2019 H1 M1 — Yes Details →
1.1.0-preview2.19309.1 05 Nov 2019 H1 M1 — Yes Details →
1.1.0-preview1.19275.1 02 Oct 2019 H1 M1 — Yes Details →
1.0.19269.1 26 Sep 2019 H1 M1 — Yes Details →
1.0.19249.1 06 Sep 2019 H1 M1 — Yes Details →
1.0.19239.1 27 Aug 2019 H1 M1 — Yes Details →
1.0.19221.1-preview 09 Aug 2019 H1 M1 — Yes Details →
1.0.19189.1-preview 08 Jul 2019 H1 M1 — Yes Details →
1.0.19128.1-preview 08 May 2019 H1 M1 — Yes Details →
1.0.19123.2-preview 06 May 2019 H1 M1 — Yes Details →
3.1.6 — none — — Details →
6.0.0 — none — — Details →
6.1.0 — none — — Details →
7.0.0-preview4.26063.3 — none — — Details →

All 116 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for Microsoft.Data.SqlClient

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About Microsoft.Data.SqlClient

Is Microsoft.Data.SqlClient safe to use?

Vulert records 2 vulnerabilities for Microsoft.Data.SqlClient in NuGet: 0 critical, 1 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is Microsoft.Data.SqlClient's Vulert package health score?

Vulert scores Microsoft.Data.SqlClient 82/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of Microsoft.Data.SqlClient affected?

No. 7.1.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of Microsoft.Data.SqlClient should I use?

7.1.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does Microsoft.Data.SqlClient have?

2 vulnerabilities are recorded for Microsoft.Data.SqlClient in the NuGet ecosystem: 0 critical, 1 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new Microsoft.Data.SqlClient vulnerabilities disclosed?

0 vulnerabilities were recorded for Microsoft.Data.SqlClient in the last 12 months, and the oldest entry in this database dates to 08 Nov 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of Microsoft.Data.SqlClient are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor Microsoft.Data.SqlClient for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the Microsoft.Data.SqlClient version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.