VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

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

Microsoft.AspNetCore.HttpOverrides is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 4 releases, first recorded in Oct 2018. 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.AspNetCore.HttpOverrides vulnerabilities

Vulert verdict on Microsoft.AspNetCore.HttpOverrides 2.3.13 i

Updated on 23 Oct 2026

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

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

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

  • Current release 2.3.13 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 16 Oct 2018 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Stars 38,474 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by NuGet, refreshed 22 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.HttpOverrides, 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.7 11 Nov 2025 none non-standard — Details →
2.3.5 05 Aug 2025 none non-standard — Details →
2.3.3 10 Jun 2025 none non-standard — Details →
2.3.0 14 Jan 2025 none non-standard — Details →
2.2.0 03 Dec 2018 none non-standard — Details →
2.2.0-preview3-35497 17 Oct 2018 none non-standard — Details →
2.2.0-preview2-35157 12 Sep 2018 none non-standard — Details →
2.2.0-preview1-35029 22 Aug 2018 none non-standard — Details →
2.1.1 18 Jun 2018 none non-standard — Details →
2.1.0 29 May 2018 none non-standard — Details →
2.0.3 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.2 13 Mar 2018 none non-standard — Details →
1.1.4 13 Mar 2018 none non-standard — Details →
1.0.5 13 Mar 2018 none non-standard — Details →
2.1.0-preview1-final 26 Feb 2018 none non-standard — Details →
2.0.1 14 Nov 2017 H1 non-standard Yes Details →
1.0.4 14 Nov 2017 none non-standard — Details →
1.1.3 20 Sep 2017 none non-standard — Details →
2.0.0 11 Aug 2017 H1 non-standard Yes Details →
2.0.0-preview2-final 27 Jun 2017 H1 non-standard Yes Details →
2.0.0-preview1-final 10 May 2017 H1 non-standard Yes Details →
1.1.2 09 May 2017 none non-standard — Details →
1.0.3 09 May 2017 none non-standard — Details →
1.1.1 06 Mar 2017 none non-standard — Details →
1.0.2 06 Mar 2017 none non-standard — Details →
1.0.1 12 Dec 2016 none non-standard — Details →
1.1.0 16 Nov 2016 none non-standard — Details →
1.1.0-preview1-final 24 Oct 2016 none non-standard — Details →
1.0.0 27 Jun 2016 none non-standard — Details →
1.0.0-rc2-final 16 May 2016 none non-standard — Details →
0.0.1-alpha — none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 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.HttpOverrides

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-0787: ASP.NET Core Elevation Of Privilege Vulnerability in Microsoft.AspNetCore.HttpOverrides and Microsoft.AspNetCore.Server.Kestrel.Core 8.8 high 2.0.2 16 Oct 2018

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.HttpOverrides

Is Microsoft.AspNetCore.HttpOverrides safe to use?

Vulert records 1 vulnerabilities for Microsoft.AspNetCore.HttpOverrides 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.AspNetCore.HttpOverrides's Vulert package health score?

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

No. 2.3.13, 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.HttpOverrides should I use?

2.3.13 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.HttpOverrides have?

1 vulnerability is recorded for Microsoft.AspNetCore.HttpOverrides 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.AspNetCore.HttpOverrides vulnerabilities disclosed?

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

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