Vulnerability Database · NuGet · Package report

Microsoft.CodeAnalysis.Workspaces.Common: vulnerability history, versions and safety

Microsoft.CodeAnalysis.Workspaces.Common is a package in the NuGet ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the NuGet ecosystem.

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.CodeAnalysis.Workspaces.Common 5.9.0 i

Updated on 23 Oct 2026

Good news: 5.9.0, the version you would install today, has no known vulnerabilities.

Package health score 89/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 5.9.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 20,747 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 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.CodeAnalysis.Workspaces.Common, 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
5.9.0 17 Aug 2026 none MIT — Details →
5.6.0 02 Jul 2026 none MIT — Details →
5.3.0 10 Mar 2026 none MIT — Details →
5.3.0-2.final 02 Feb 2026 none MIT — Details →
5.0.0 18 Nov 2025 none MIT — Details →
5.0.0-2.final 09 Oct 2025 none MIT — Details →
4.14.0 15 May 2025 none MIT — Details →
4.13.0 24 Feb 2025 none MIT — Details →
4.12.0 04 Dec 2024 none MIT — Details →
4.12.0-3.final 29 Oct 2024 none MIT — Details →
4.12.0-2.final 17 Sep 2024 none MIT — Details →
4.11.0 15 Aug 2024 none MIT — Details →
4.12.0-1.final 14 Aug 2024 none MIT — Details →
4.11.0-3.final 31 Jul 2024 none MIT — Details →
4.11.0-2.final 19 Jun 2024 none MIT — Details →
4.10.0 10 Jun 2024 none MIT — Details →
4.10.0-3.final 29 Apr 2024 none MIT — Details →
4.10.0-2.final 19 Mar 2024 none MIT — Details →
4.10.0-1.final 18 Mar 2024 none MIT — Details →
4.9.2 02 Mar 2024 none MIT — Details →
4.9.0-3.final 22 Jan 2024 none MIT — Details →
4.9.0-2.final 16 Dec 2023 none MIT — Details →
4.9.0-1.final 13 Dec 2023 none MIT — Details →
4.8.0 22 Nov 2023 none MIT — Details →
4.8.0-3.final 03 Nov 2023 none MIT — Details →
4.8.0-2.final 20 Sep 2023 none MIT — Details →
4.8.0-1.final 09 Sep 2023 none MIT — Details →
4.7.0 18 Aug 2023 none MIT — Details →
4.7.0-2.final 20 Jun 2023 none MIT — Details →
4.7.0-1.final 20 May 2023 none MIT — Details →
4.6.0 16 May 2023 none MIT — Details →
4.6.0-1.final 03 Mar 2023 none MIT — Details →
4.5.0 24 Feb 2023 none MIT — Details →
4.5.0-2.final 06 Jan 2023 none MIT — Details →
4.4.0 14 Nov 2022 none MIT — Details →
4.4.0-4.final 22 Oct 2022 none MIT — Details →
4.3.1 30 Sep 2022 none MIT — Details →
4.4.0-2.final 19 Sep 2022 none MIT — Details →
4.4.0-1.final 16 Aug 2022 none MIT — Details →
4.3.0-3.final 26 Jul 2022 none MIT — Details →
4.3.0-2.final 22 Jun 2022 none MIT — Details →
4.2.0 13 May 2022 none MIT — Details →
4.3.0-1.final 10 May 2022 none MIT — Details →
4.2.0-4.final 27 Apr 2022 none MIT — Details →
4.2.0-2.final 25 Mar 2022 none MIT — Details →
4.2.0-1.final 18 Feb 2022 none MIT — Details →
4.1.0 16 Feb 2022 none MIT — Details →
4.1.0-3.final 27 Jan 2022 none MIT — Details →
4.1.0-1.final 19 Nov 2021 none MIT — Details →
4.0.1 09 Nov 2021 none MIT — Details →
4.0.0-6.final 20 Oct 2021 none MIT — Details →
4.0.0-5.final 11 Oct 2021 none MIT — Details →
4.0.0-4.final 15 Sep 2021 none MIT — Details →
4.0.0-3.final 12 Aug 2021 none MIT — Details →
3.11.0 11 Aug 2021 none MIT — Details →
4.0.0-2.final 20 Jul 2021 none MIT — Details →
3.11.0-3.final 15 Jul 2021 none MIT — Details →
4.0.0-1.final 07 Jul 2021 none MIT — Details →
3.11.0-1.final 14 Jun 2021 none MIT — Details →
3.10.0 11 Jun 2021 none MIT — Details →
3.10.0-3.final 13 May 2021 none MIT — Details →
3.10.0-2.final 20 Apr 2021 none MIT — Details →
3.10.0-1.final 03 Mar 2021 none MIT — Details →
3.9.0 02 Mar 2021 none MIT — Details →
3.9.0-5.final 24 Feb 2021 none MIT — Details →
3.9.0-4.final 10 Feb 2021 none MIT — Details →
3.9.0-3.final 20 Jan 2021 none MIT — Details →
3.9.0-2.final 10 Dec 2020 none MIT — Details →
3.9.0-1.final 04 Dec 2020 none MIT — Details →
3.8.0 13 Nov 2020 none MIT — Details →
3.8.0-5.final 23 Oct 2020 none MIT — Details →
3.8.0-4.final 13 Oct 2020 none MIT — Details →
3.8.0-3.final 16 Sep 2020 none MIT — Details →
3.8.0-2.final 01 Sep 2020 none MIT — Details →
3.7.0 05 Aug 2020 none MIT — Details →
3.7.0-4.final 14 Jul 2020 none MIT — Details →
3.7.0-3.final 02 Jul 2020 none MIT — Details →
3.7.0-2.final 15 Jun 2020 none MIT — Details →
3.7.0-1.final 19 May 2020 none MIT — Details →
3.6.0 19 May 2020 none MIT — Details →
3.6.0-4.final 05 May 2020 none MIT — Details →
3.6.0-3.final 16 Apr 2020 none MIT — Details →
3.6.0-2.final 26 Mar 2020 none MIT — Details →
3.6.0-1.final 17 Mar 2020 none MIT — Details →
3.5.0 16 Mar 2020 none MIT — Details →
3.5.0-beta3-final 19 Feb 2020 none MIT — Details →
3.5.0-beta2-final 23 Jan 2020 none Apache-2.0 — Details →
3.5.0-beta1-final 03 Dec 2019 none Apache-2.0 — Details →
3.4.0 03 Dec 2019 none Apache-2.0 — Details →
3.4.0-beta4-final 15 Nov 2019 none Apache-2.0 — Details →
3.4.0-beta3-final 04 Nov 2019 none Apache-2.0 — Details →
3.4.0-beta2-final 15 Oct 2019 none Apache-2.0 — Details →
3.4.0-beta1-final 23 Sep 2019 none Apache-2.0 — Details →
3.3.1 23 Sep 2019 none Apache-2.0 — Details →
3.3.1-beta3-final 05 Sep 2019 none Apache-2.0 — Details →
3.3.0-beta2-final 15 Aug 2019 none Apache-2.0 — Details →
3.2.1 09 Aug 2019 none Apache-2.0 — Details →
3.2.0 01 Aug 2019 none Apache-2.0 — Details →
3.3.0-beta1-final 26 Jul 2019 none Apache-2.0 — Details →
3.2.0-beta4-final 16 Jul 2019 none Apache-2.0 — Details →
3.2.0-beta3-final 25 Jun 2019 none — — Details →
3.2.0-beta1-final 21 May 2019 none — — Details →
3.1.0 21 May 2019 none — — Details →
3.1.0-beta3-final 07 May 2019 none — — Details →
3.1.0-beta2-final 24 Apr 2019 none — — Details →
3.1.0-beta1-final 10 Apr 2019 none — — Details →
3.0.0 02 Apr 2019 none — — Details →
3.0.0-beta4-final 27 Feb 2019 none — — Details →
3.0.0-beta3-final 14 Feb 2019 none — — Details →
3.0.0-beta2-final 24 Jan 2019 none — — Details →
2.11.0-beta1-final 11 Dec 2018 none — — Details →
2.10.0 15 Nov 2018 none — — Details →
2.9.0 16 Aug 2018 none — — Details →
2.8.2 22 May 2018 none — — Details →
2.8.0 01 May 2018 none — — Details →
2.8.0-beta4 20 Apr 2018 none — — Details →
2.8.0-beta3 12 Apr 2018 none — — Details →
2.7.0 08 Mar 2018 none — — Details →
2.6.1 14 Dec 2017 none — — Details →
2.6.0 08 Dec 2017 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for Microsoft.CodeAnalysis.Workspaces.Common

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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.CodeAnalysis.Workspaces.Common

Is Microsoft.CodeAnalysis.Workspaces.Common safe to use?

Vulert has no vulnerabilities on record for Microsoft.CodeAnalysis.Workspaces.Common in NuGet at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is Microsoft.CodeAnalysis.Workspaces.Common's Vulert package health score?

Vulert scores Microsoft.CodeAnalysis.Workspaces.Common 89/100, which reads as healthy. 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.CodeAnalysis.Workspaces.Common affected?

No. 5.9.0, 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.CodeAnalysis.Workspaces.Common should I use?

5.9.0 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.CodeAnalysis.Workspaces.Common have?

0 vulnerabilities are recorded for Microsoft.CodeAnalysis.Workspaces.Common in the NuGet ecosystem: 0 critical, 0 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.CodeAnalysis.Workspaces.Common vulnerabilities disclosed?

0 vulnerabilities were recorded for Microsoft.CodeAnalysis.Workspaces.Common in the last 12 months. 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.CodeAnalysis.Workspaces.Common 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.CodeAnalysis.Workspaces.Common for upcoming vulnerabilities?

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