Vulnerability Database · NuGet · Package report
Microsoft.AspNet.Web.Optimization: vulnerability history, versions and safety
Microsoft.AspNet.Web.Optimization is a package in the NuGet ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the NuGet ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on Microsoft.AspNet.Web.Optimization 1.1.3 i
Updated on 23 Oct 2026
Good news: 1.1.3, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Deprecated
- Popularity Not enough data
- Community Not enough data
The registry marks the latest release as deprecated, which caps this score.
What to do: Stay on 1.1.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.1.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 1.1.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Last release 152 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.AspNet.Web.Optimization, 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.
- 1.1.3 20 Feb 2014
- 1.1.2 31 Oct 2013
- 1.1.1 10 Oct 2013
- 1.1.0 26 Jun 2013
- 1.1.0-beta1 12 Mar 2013
- 1.1.0-alpha1 19 Oct 2012
- 1.0.0 11 Aug 2012
- 1.0.0-beta3 14 Jun 2012
- 1.0.0-beta2 31 May 2012
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 1.1.3 | 20 Feb 2014 | none | non-standard | — | Details → |
| 1.1.2 | 31 Oct 2013 | none | non-standard | — | Details → |
| 1.1.1 | 10 Oct 2013 | none | non-standard | — | Details → |
| 1.1.0 | 26 Jun 2013 | none | non-standard | — | Details → |
| 1.1.0-beta1 | 12 Mar 2013 | none | non-standard | — | Details → |
| 1.1.0-alpha1 | 19 Oct 2012 | none | non-standard | — | Details → |
| 1.0.0 | 11 Aug 2012 | none | non-standard | — | Details → |
| 1.0.0-beta3 | 14 Jun 2012 | none | non-standard | — | Details → |
| 1.0.0-beta2 | 31 May 2012 | none | non-standard | — | Details → |
All 9 versions Vulert tracks for this package. 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.AspNet.Web.Optimization
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
Questions
About Microsoft.AspNet.Web.Optimization
Is Microsoft.AspNet.Web.Optimization safe to use?
Vulert has no vulnerabilities on record for Microsoft.AspNet.Web.Optimization 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.AspNet.Web.Optimization's Vulert package health score?
Vulert scores Microsoft.AspNet.Web.Optimization 45/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.
Is the latest version of Microsoft.AspNet.Web.Optimization affected?
No. 1.1.3, 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.AspNet.Web.Optimization should I use?
1.1.3 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.AspNet.Web.Optimization have?
0 vulnerabilities are recorded for Microsoft.AspNet.Web.Optimization 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.AspNet.Web.Optimization vulnerabilities disclosed?
0 vulnerabilities were recorded for Microsoft.AspNet.Web.Optimization 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.AspNet.Web.Optimization 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.AspNet.Web.Optimization for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the Microsoft.AspNet.Web.Optimization version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.