VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Microsoft.Bot.Connector: vulnerability history, versions and safety

Microsoft.Bot.Connector is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 4 releases, first recorded in Mar 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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.

See all Microsoft.Bot.Connector vulnerabilities

Vulert verdict on Microsoft.Bot.Connector 4.23.1 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 4.23.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 08 Mar 2021 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 902 i
  • OpenSSF scorecard 3/10 i
  • Last release 9 months ago 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.Bot.Connector, 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
4.23.1 05 Jan 2026 none MIT — Details →
4.23.0 23 Jan 2025 none MIT — Details →
4.22.9 19 Sep 2024 none MIT — Details →
4.22.8 10 Sep 2024 none MIT — Details →
4.22.7 25 Jun 2024 none MIT — Details →
4.22.4 30 May 2024 none MIT — Details →
4.22.3 15 Apr 2024 none MIT — Details →
4.22.2 15 Feb 2024 none MIT — Details →
4.22.1 06 Feb 2024 none MIT — Details →
4.22.0 25 Jan 2024 none MIT — Details →
4.21.2 27 Nov 2023 none MIT — Details →
4.17.5 06 Nov 2023 none MIT — Details →
4.21.1 18 Oct 2023 none MIT — Details →
4.21.0 18 Sep 2023 none MIT — Details →
4.20.1 13 Jul 2023 none MIT — Details →
4.17.3 11 Jul 2023 none MIT — Details →
4.20.0 01 Jun 2023 none MIT — Details →
4.19.3 02 Mar 2023 none MIT — Details →
4.19.2 16 Feb 2023 none MIT — Details →
4.19.1 17 Jan 2023 none MIT — Details →
4.19.0 11 Jan 2023 none MIT — Details →
4.18.1 26 Oct 2022 none MIT — Details →
4.17.2 14 Sep 2022 none MIT — Details →
4.17.1 03 Aug 2022 none MIT — Details →
4.17.0 02 Aug 2022 none MIT — Details →
4.16.1 17 May 2022 none MIT — Details →
4.16.0 14 Apr 2022 none MIT — Details →
4.15.2 07 Feb 2022 none MIT — Details →
4.15.1 14 Dec 2021 none MIT — Details →
4.9.7 19 Nov 2021 none non-standard — Details →
4.10.7 19 Nov 2021 none non-standard — Details →
4.11.3 19 Nov 2021 none non-standard — Details →
4.12.4 19 Nov 2021 none non-standard — Details →
4.14.4 19 Nov 2021 none MIT — Details →
4.13.8 17 Nov 2021 none non-standard — Details →
4.15.0 15 Nov 2021 none MIT — Details →
4.13.5 07 Sep 2021 none non-standard — Details →
4.13.4 26 Jul 2021 none non-standard — Details →
4.14.1 08 Jul 2021 none MIT — Details →
4.14.0 01 Jul 2021 none MIT — Details →
4.8.3 21 Jun 2021 none non-standard — Details →
4.9.6 21 Jun 2021 none non-standard — Details →
4.10.6 21 Jun 2021 none non-standard — Details →
4.11.2 21 Jun 2021 none non-standard — Details →
4.12.3 21 Jun 2021 none non-standard — Details →
4.13.3 15 Jun 2021 none non-standard — Details →
4.13.2 18 May 2021 none non-standard — Details →
4.13.1 28 Apr 2021 none non-standard — Details →
4.13.0 15 Apr 2021 none non-standard — Details →
4.12.2 17 Mar 2021 none non-standard — Details →
4.12.1 10 Mar 2021 none non-standard — Details →
4.12.0 04 Mar 2021 none non-standard — Details →
4.6.4 02 Dec 2020 none non-standard — Details →
4.11.1 17 Nov 2020 none non-standard — Details →
4.8.2 17 Nov 2020 none non-standard — Details →
4.9.5 13 Nov 2020 none non-standard — Details →
4.7.3 10 Nov 2020 none non-standard — Details →
4.11.0 09 Nov 2020 none non-standard — Details →
4.10.3 09 Sep 2020 none non-standard — Details →
4.10.2 27 Aug 2020 none non-standard — Details →
4.10.0 17 Aug 2020 none non-standard — Details →
4.9.4 22 Jul 2020 none non-standard — Details →
4.9.3 02 Jun 2020 none non-standard — Details →
4.9.2 28 May 2020 none non-standard — Details →
4.9.1 14 May 2020 none non-standard — Details →
4.9.0 12 May 2020 none non-standard — Details →
3.30.0 19 Mar 2020 none non-standard — Details →
4.8.0 17 Mar 2020 none non-standard — Details →
4.7.2 23 Jan 2020 none non-standard — Details →
4.7.1 14 Jan 2020 none non-standard — Details →
4.7.0 13 Dec 2019 none non-standard — Details →
4.6.3 14 Nov 2019 H1 non-standard Yes Details →
4.6.2 06 Nov 2019 H1 non-standard Yes Details →
4.6.1 04 Nov 2019 H1 non-standard Yes Details →
4.6.0 30 Oct 2019 H1 non-standard Yes Details →
4.5.3 03 Oct 2019 none non-standard — Details →
4.5.2 11 Sep 2019 none non-standard — Details →
4.5.1 17 Jul 2019 none non-standard — Details →
4.5.0 10 Jul 2019 none non-standard — Details →
4.4.5 13 Jun 2019 none non-standard — Details →
4.4.4 23 May 2019 none non-standard — Details →
4.4.3 04 May 2019 none non-standard — Details →
4.3.2 12 Mar 2019 none non-standard — Details →
4.3.1 04 Mar 2019 none non-standard — Details →
4.2.2 30 Jan 2019 none non-standard — Details →
3.20.1 23 Jan 2019 none non-standard — Details →
3.19.2 22 Jan 2019 none non-standard — Details →
4.2.0 11 Dec 2018 none non-standard — Details →
3.19.1.44133 26 Nov 2018 none non-standard — Details →
4.1.5 05 Nov 2018 none non-standard — Details →
3.17.0.42969 05 Nov 2018 none non-standard — Details →
4.1.1 31 Oct 2018 none non-standard — Details →
4.0.8 16 Oct 2018 none non-standard — Details →
4.0.7 23 Sep 2018 none non-standard — Details →
4.0.6 22 Sep 2018 none non-standard — Details →
3.16.1.38846 06 Sep 2018 none non-standard — Details →
3.16.0.38344 24 Aug 2018 none non-standard — Details →
3.15.3 29 Jun 2018 none non-standard — Details →
3.15.2.3 28 Jun 2018 none non-standard — Details →
3.15.2.2 08 May 2018 none non-standard — Details →
3.15.2.1 06 May 2018 none — — Details →
3.15.2 05 May 2018 none — — Details →
3.15.1 04 May 2018 none — — Details →
4.0.1-preview 04 May 2018 none — — Details →
4.0.0-preview 03 May 2018 none — — Details →
4.0.0-alpham4.2 02 May 2018 none — — Details →
4.0.0-alpham4 30 Apr 2018 none — — Details →
4.0.0-alpham3.2 22 Apr 2018 none — — Details →
4.0.0-alpha-m3.1 14 Apr 2018 none — — Details →
4.0.0-alpha-m3 14 Apr 2018 none — — Details →
3.15.0 14 Apr 2018 none — — Details →
3.14.1.1 20 Mar 2018 none — — Details →
3.14.0.7 08 Mar 2018 none — — Details →
3.13.1 07 Feb 2018 none — — Details →
3.13.0.3 31 Jan 2018 none — — Details →
3.12.2.4 28 Nov 2017 none — — Details →
3.11.1 07 Oct 2017 none — — Details →
1.0.0 — none — — Details →
1.1.0 — none — — Details →
3.11.0 — none — — Details →

The newest 120 of 132 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1

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

03 Vulnerabilities

Recorded vulnerabilities for Microsoft.Bot.Connector

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Improper Authentication in Microsoft.Bot.Connector N/A high 4.6.4 08 Mar 2021

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.Bot.Connector

Is Microsoft.Bot.Connector safe to use?

Vulert records 1 vulnerabilities for Microsoft.Bot.Connector in NuGet: 0 critical, 1 high, 0 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.Bot.Connector's Vulert package health score?

Vulert scores Microsoft.Bot.Connector 77/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.Bot.Connector affected?

No. 4.23.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.Bot.Connector should I use?

4.23.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.Bot.Connector have?

1 vulnerability is recorded for Microsoft.Bot.Connector in the NuGet ecosystem: 0 critical, 1 high, 0 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.Bot.Connector vulnerabilities disclosed?

0 vulnerabilities were recorded for Microsoft.Bot.Connector in the last 12 months, and the oldest entry in this database dates to 08 Mar 2021. 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.Bot.Connector 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.Bot.Connector for upcoming vulnerabilities?

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