VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Refit: vulnerability history, versions and safety

Refit is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 77 releases, first recorded in Nov 2024. 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 C1
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 Refit vulnerabilities

Vulert verdict on Refit 16.4.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 16.4.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 04 Nov 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 9,577 i
  • OpenSSF scorecard 5/10 i
  • Last release this month 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 Refit, 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
16.4.0 17 Oct 2026 none MIT — Details →
16.3.0 26 Sep 2026 none MIT — Details →
16.2.0 26 Sep 2026 none MIT — Details →
16.1.0 21 Sep 2026 none MIT — Details →
16.0.0 20 Sep 2026 none MIT — Details →
15.2.0 18 Aug 2026 none MIT — Details →
15.1.0 15 Aug 2026 none MIT — Details →
15.0.0 05 Aug 2026 none MIT — Details →
15.0.0-beta.1 03 Aug 2026 none MIT — Details →
14.0.1 26 Jul 2026 none MIT — Details →
14.0.0 25 Jul 2026 none MIT — Details →
14.0.0-beta.5 22 Jul 2026 none MIT — Details →
14.0.0-beta.4 20 Jul 2026 none MIT — Details →
14.0.0-beta.3 20 Jul 2026 none MIT — Details →
14.0.0-beta.2 16 Jul 2026 none MIT — Details →
14.0.0-beta.1 15 Jul 2026 none MIT — Details →
13.1.0 03 Jul 2026 none MIT — Details →
13.0.0 01 Jul 2026 none MIT — Details →
12.1.0 29 Jun 2026 none MIT — Details →
12.0.0 24 Jun 2026 none MIT — Details →
11.2.0 18 Jun 2026 none MIT — Details →
11.1.0 17 Jun 2026 none MIT — Details →
11.0.1 04 Jun 2026 none MIT — Details →
11.0.0 03 Jun 2026 none MIT — Details →
10.2.0 03 Jun 2026 none MIT — Details →
10.1.7 03 Jun 2026 none MIT — Details →
10.1.6 21 Mar 2026 none MIT — Details →
10.0.1 06 Feb 2026 none MIT — Details →
9.0.2 30 Nov 2025 none MIT — Details →
7.2.22 08 Nov 2024 none MIT — Details →
8.0.0 03 Nov 2024 none MIT — Details →
7.2.1 19 Sep 2024 C1 MIT Yes Details →
7.2.0 16 Sep 2024 C1 MIT Yes Details →
7.1.2 30 Jun 2024 C1 MIT Yes Details →
7.0.0 29 Jun 2023 C1 MIT Yes Details →
6.3.2 08 Feb 2022 C1 MIT Yes Details →
6.2.16 26 Jan 2022 C1 MIT Yes Details →
6.1.15 14 Oct 2021 C1 MIT Yes Details →
6.0.94 05 Aug 2021 C1 MIT Yes Details →
6.0.38 19 Mar 2021 C1 MIT Yes Details →
6.0.24 23 Feb 2021 C1 MIT Yes Details →
6.0.21 23 Feb 2021 C1 MIT Yes Details →
6.0.15 11 Feb 2021 C1 MIT Yes Details →
6.0.8 10 Feb 2021 C1 MIT Yes Details →
6.0.1 08 Feb 2021 C1 MIT Yes Details →
6.0.0-preview.128 04 Feb 2021 C1 MIT Yes Details →
6.0.0-preview.96 25 Jan 2021 C1 MIT Yes Details →
5.2.4 26 Nov 2020 C1 MIT Yes Details →
6.0.0-preview.37 26 Nov 2020 C1 MIT Yes Details →
5.2.1 05 Sep 2020 C1 MIT Yes Details →
5.1.67 08 Apr 2020 C1 MIT Yes Details →
5.1.54 01 Apr 2020 C1 MIT Yes Details →
5.1.27 23 Mar 2020 C1 MIT Yes Details →
5.0.23 18 Nov 2019 C1 MIT Yes Details →
5.0.15 14 Nov 2019 C1 MIT Yes Details →
4.8.14 31 Oct 2019 C1 MIT Yes Details →
4.7.51 20 Aug 2019 C1 MIT Yes Details →
4.7.9 05 Jun 2019 C1 MIT Yes Details →
4.6.107 12 Apr 2019 C1 MIT Yes Details →
4.6.99 12 Mar 2019 C1 MIT Yes Details →
4.6.90 18 Feb 2019 C1 MIT Yes Details →
4.6.58 23 Nov 2018 C1 non-standard Yes Details →
4.6.48 05 Oct 2018 C1 non-standard Yes Details →
4.6.30 31 Jul 2018 C1 non-standard Yes Details →
4.6.16 20 Jun 2018 C1 non-standard Yes Details →
4.5.6 23 May 2018 C1 non-standard Yes Details →
4.4.17 15 May 2018 C1 non-standard Yes Details →
4.3.0 17 Feb 2018 C1 non-standard Yes Details →
4.2.0 31 Jan 2018 C1 non-standard Yes Details →
4.1.0 14 Jan 2018 C1 non-standard Yes Details →
4.0.1 27 Aug 2017 C1 non-standard Yes Details →
4.0.0 15 Aug 2017 C1 non-standard Yes Details →
3.1.0 06 Jun 2017 C1 non-standard Yes Details →
3.0.1 03 Oct 2016 C1 non-standard Yes Details →
3.0.0 15 Aug 2016 C1 non-standard Yes Details →
2.4.1 29 Sep 2015 C1 non-standard Yes Details →
2.4.0 24 Sep 2015 C1 non-standard Yes Details →
2.3.0 01 Jun 2015 C1 non-standard Yes Details →
2.2.1 08 Feb 2015 C1 non-standard Yes Details →
2.2.0 03 Jan 2015 C1 non-standard Yes Details →
2.1.0 14 Nov 2014 C1 non-standard Yes Details →
2.0.2 13 Oct 2014 C1 non-standard Yes Details →
2.0.1 13 Oct 2014 C1 non-standard Yes Details →
2.0.0 12 Oct 2014 C1 non-standard Yes Details →
1.3.0 25 Jul 2014 C1 non-standard Yes Details →
1.2.0 20 Jun 2014 C1 non-standard Yes Details →
1.1.0 02 May 2014 C1 non-standard Yes Details →
1.0.0 30 Jul 2013 C1 non-standard Yes Details →
10.1.6-gd3b9f6eb22 — none MIT — Details →
4.0.0-build.11 — C1 non-standard Yes Details →
4.0.0-build.14 — C1 non-standard Yes Details →
4.0.0-build.16 — C1 non-standard Yes Details →
4.5.4 — C1 non-standard Yes Details →
4.6.15 — C1 non-standard Yes Details →
4.6.85 — C1 MIT Yes Details →
4.7.5 — C1 MIT Yes Details →
5.1.26 — C1 MIT Yes Details →
6.0.0-preview.121 — C1 MIT Yes Details →
6.0.0-preview.124 — C1 MIT Yes Details →
6.0.0-preview.34 — C1 MIT Yes Details →
6.0.0-preview.84 — C1 — Yes Details →
6.0.0-preview.86 — C1 — Yes Details →
6.0.0-preview.94 — C1 — Yes Details →
6.2.14 — C1 — Yes Details →
6.4.1 — C1 — Yes Details →
6.5.1 — C1 — Yes Details →
7.0.0-beta.1 — C1 — Yes Details →
7.1.0 — C1 — Yes Details →
7.1.1 — C1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 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 Refit

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-51501: Refit CRLF Injection Vulnerability in Header Attributes 9.8 critical 7.2.22 04 Nov 2024

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 Refit

Is Refit safe to use?

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

Vulert scores Refit 83/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 Refit affected?

No. 16.4.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.

How many vulnerabilities does Refit have?

1 vulnerability is recorded for Refit in the NuGet ecosystem: 1 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 Refit vulnerabilities disclosed?

0 vulnerabilities were recorded for Refit in the last 12 months, and the oldest entry in this database dates to 04 Nov 2024. 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 Refit 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 Refit for upcoming vulnerabilities?

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