Vulnerability Database · NuGet · Package report

Microsoft.AspNetCore.SpaServices: vulnerability history, versions and safety

Microsoft.AspNetCore.SpaServices is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 4 releases, first recorded in May 2022. 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 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.AspNetCore.SpaServices 3.1.32 i

Updated on 23 Oct 2026

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

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

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

  • Current release 3.1.32 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 38,474 i
  • OpenSSF scorecard 5/10 i
  • Last release 46 months ago i
  • Licence non-standard 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.AspNetCore.SpaServices, 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
2.3.13 08 Sep 2026 none non-standard — Details →
2.3.12 11 Aug 2026 none non-standard — Details →
2.3.11 09 Jun 2026 none non-standard — Details →
2.3.10 12 May 2026 none non-standard — Details →
2.3.9 07 Jan 2026 none non-standard — Details →
2.3.8 07 Jan 2026 none non-standard — Details →
2.3.0 14 Jan 2025 none non-standard — Details →
3.1.32 13 Dec 2022 none Apache-2.0 — Details →
3.1.31 08 Nov 2022 none Apache-2.0 — Details →
3.1.30 11 Oct 2022 none Apache-2.0 — Details →
3.1.29 13 Sep 2022 none Apache-2.0 — Details →
3.1.28 09 Aug 2022 none Apache-2.0 — Details →
3.1.27 12 Jul 2022 none Apache-2.0 — Details →
3.1.26 14 Jun 2022 none Apache-2.0 — Details →
3.1.25 10 May 2022 none Apache-2.0 — Details →
3.1.24 11 Apr 2022 none Apache-2.0 — Details →
3.1.23 08 Mar 2022 none Apache-2.0 — Details →
3.1.22 14 Dec 2021 none Apache-2.0 — Details →
3.1.21 07 Nov 2021 none Apache-2.0 — Details →
3.1.20 11 Oct 2021 none Apache-2.0 — Details →
3.1.19 14 Sep 2021 none Apache-2.0 — Details →
3.1.18 10 Aug 2021 none Apache-2.0 — Details →
3.1.17 13 Jul 2021 none Apache-2.0 — Details →
3.1.16 08 Jun 2021 none Apache-2.0 — Details →
3.1.15 11 May 2021 none Apache-2.0 — Details →
3.1.14 06 Apr 2021 none Apache-2.0 — Details →
3.1.13 09 Mar 2021 none Apache-2.0 — Details →
3.1.12 09 Feb 2021 none Apache-2.0 — Details →
3.1.11 12 Jan 2021 none Apache-2.0 — Details →
3.1.10 09 Nov 2020 none Apache-2.0 — Details →
3.1.9 13 Oct 2020 none Apache-2.0 — Details →
3.1.8 08 Sep 2020 none Apache-2.0 — Details →
5.0.0-preview.8.20414.8 25 Aug 2020 none Apache-2.0 — Details →
3.1.7 11 Aug 2020 none Apache-2.0 — Details →
5.0.0-preview.7.20365.19 21 Jul 2020 none Apache-2.0 — Details →
3.1.6 14 Jul 2020 none Apache-2.0 — Details →
5.0.0-preview.6.20312.15 25 Jun 2020 none Apache-2.0 — Details →
5.0.0-preview.5.20279.2 10 Jun 2020 none Apache-2.0 — Details →
3.1.5 09 Jun 2020 none Apache-2.0 — Details →
5.0.0-preview.4.20257.10 18 May 2020 none Apache-2.0 — Details →
3.1.4 12 May 2020 none Apache-2.0 — Details →
5.0.0-preview.3.20215.14 23 Apr 2020 none Apache-2.0 — Details →
5.0.0-preview.2.20167.3 02 Apr 2020 none Apache-2.0 — Details →
3.1.3 24 Mar 2020 none Apache-2.0 — Details →
5.0.0-preview.1.20124.5 16 Mar 2020 none Apache-2.0 — Details →
3.1.2 18 Feb 2020 none Apache-2.0 — Details →
3.0.3 18 Feb 2020 none Apache-2.0 — Details →
3.1.1 14 Jan 2020 none Apache-2.0 — Details →
3.0.2 14 Jan 2020 none Apache-2.0 — Details →
3.1.0 03 Dec 2019 none Apache-2.0 — Details →
3.1.0-preview3.19555.2 13 Nov 2019 none Apache-2.0 — Details →
3.1.0-preview2.19528.8 01 Nov 2019 none Apache-2.0 — Details →
3.1.0-preview1.19508.20 15 Oct 2019 none Apache-2.0 — Details →
3.0.0 23 Sep 2019 none Apache-2.0 — Details →
3.0.0-rc1.19457.4 16 Sep 2019 none Apache-2.0 — Details →
2.1.13 10 Sep 2019 none non-standard — Details →
2.2.7 10 Sep 2019 none non-standard — Details →
3.0.0-preview9.19424.4 04 Sep 2019 none Apache-2.0 — Details →
3.0.0-preview8.19405.7 13 Aug 2019 none Apache-2.0 — Details →
3.0.0-preview7.19365.7 23 Jul 2019 none Apache-2.0 — Details →
3.0.0-preview6.19307.2 12 Jun 2019 none non-standard — Details →
3.0.0-preview5-19227-01 06 May 2019 none non-standard — Details →
3.0.0-preview4-19216-03 18 Apr 2019 none non-standard — Details →
3.0.0-preview3-19153-02 06 Mar 2019 none non-standard — Details →
3.0.0-preview-19075-0444 29 Jan 2019 none non-standard — Details →
3.0.0-preview-18579-0056 03 Dec 2018 none non-standard — Details →
2.2.0 03 Dec 2018 M1 non-standard Yes Details →
2.2.0-preview3-35497 17 Oct 2018 M1 non-standard Yes Details →
2.2.0-preview2-35157 12 Sep 2018 M1 non-standard Yes Details →
2.2.0-preview1-35029 22 Aug 2018 M1 non-standard Yes Details →
2.1.1 18 Jun 2018 none non-standard — Details →
2.1.0 29 May 2018 none non-standard — Details →
2.0.4 07 May 2018 none non-standard — Details →
2.1.0-rc1-final 06 May 2018 none non-standard — Details →
2.1.0-preview2-final 10 Apr 2018 none non-standard — Details →
2.0.3 13 Mar 2018 none non-standard — Details →
2.1.0-preview1-final 26 Feb 2018 none non-standard — Details →
2.0.2 09 Jan 2018 none non-standard — Details →
2.0.1 14 Nov 2017 none non-standard — Details →
2.0.0 11 Aug 2017 none non-standard — Details →
2.0.0-preview2-final 28 Jun 2017 none non-standard — Details →
1.1.1 04 May 2017 none non-standard — Details →
1.1.0 30 Jan 2017 none non-standard — Details →
1.1.0-rc2-final 24 Jan 2017 none non-standard — Details →
1.1.0-rc1-final 13 Jan 2017 none non-standard — Details →
1.1.0-beta-000002 30 Nov 2016 none — — Details →
1.0.0-beta-000021 29 Nov 2016 none — — Details →
1.0.0-beta-000020 28 Nov 2016 none — — Details →
1.1.0-beta-000001 21 Nov 2016 none — — Details →
1.0.0-beta-000019 28 Sep 2016 none — — Details →
1.0.0-beta-000018 27 Sep 2016 none — — Details →
1.0.0-beta-000017 27 Sep 2016 none — — Details →
1.0.0-beta-000016 21 Sep 2016 none — — Details →
1.0.0-beta-000015 21 Sep 2016 none — — Details →
1.0.0-beta-000014 15 Sep 2016 none — — Details →
1.0.0-beta-000013 13 Sep 2016 none — — Details →
1.0.0-beta-000012 09 Sep 2016 none — — Details →
1.0.0-beta-000011 18 Aug 2016 none — — Details →
1.0.0-beta-000010 08 Aug 2016 none — — Details →
1.0.0-beta-000009 27 Jul 2016 none — — Details →
1.0.0-beta-000008 26 Jul 2016 none — — Details →
1.0.0-beta-000007 07 Jul 2016 none — — Details →
1.0.0-beta-000006 28 Jun 2016 none — — Details →
1.0.0-beta-000005 21 Jun 2016 none — — Details →
1.0.0-beta-000004 14 Jun 2016 none — — Details →
1.0.0-beta-000003 07 Jun 2016 none — — Details →
1.0.0-beta-000002 17 May 2016 none — — Details →
1.0.0-beta-000001 08 Apr 2016 none — — Details →

All 108 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

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.AspNetCore.SpaServices

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 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.AspNetCore.SpaServices

Is Microsoft.AspNetCore.SpaServices safe to use?

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

Vulert scores Microsoft.AspNetCore.SpaServices 81/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.AspNetCore.SpaServices affected?

No. 3.1.32, 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.AspNetCore.SpaServices should I use?

3.1.32 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.AspNetCore.SpaServices have?

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

0 vulnerabilities were recorded for Microsoft.AspNetCore.SpaServices in the last 12 months, and the oldest entry in this database dates to 24 May 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.AspNetCore.SpaServices 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.AspNetCore.SpaServices for upcoming vulnerabilities?

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