VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Hangfire.Core: vulnerability history, versions and safety

Hangfire.Core is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 1 release, first recorded in Nov 2021. 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 Hangfire.Core vulnerabilities

Vulert verdict on Hangfire.Core 1.8.25 i

Updated on 23 Oct 2026

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

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

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

  • Current release 1.8.25 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 03 Nov 2021 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Stars 10,150 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month 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 Hangfire.Core, 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
1.8.25 28 Aug 2026 none non-standard — Details →
1.8.24 16 Jul 2026 none non-standard — Details →
1.8.23 05 Feb 2026 none non-standard — Details →
1.8.22 07 Nov 2025 none non-standard — Details →
1.8.21 12 Aug 2025 none non-standard — Details →
1.8.20 16 May 2025 none non-standard — Details →
1.8.19 16 May 2025 none non-standard — Details →
1.8.18 17 Feb 2025 none non-standard — Details →
1.8.17 03 Dec 2024 none non-standard — Details →
1.8.16 27 Nov 2024 none non-standard — Details →
1.8.15 23 Oct 2024 none non-standard — Details →
1.8.14 11 Jun 2024 none non-standard — Details →
1.7.37 08 Apr 2024 none non-standard — Details →
1.8.12 03 Apr 2024 none non-standard — Details →
1.8.11 23 Feb 2024 none non-standard — Details →
1.8.10 12 Feb 2024 none non-standard — Details →
1.8.9 24 Jan 2024 none non-standard — Details →
1.8.7 29 Dec 2023 none non-standard — Details →
1.8.6 18 Oct 2023 none non-standard — Details →
1.8.5 11 Aug 2023 none non-standard — Details →
1.8.4 27 Jul 2023 none non-standard — Details →
1.7.36 29 Jun 2023 none non-standard — Details →
1.8.3 27 Jun 2023 none non-standard — Details →
1.8.2 26 May 2023 none non-standard — Details →
1.8.1 18 May 2023 none non-standard — Details →
1.7.35 18 May 2023 none non-standard — Details →
1.8.0 28 Apr 2023 none non-standard — Details →
1.7.34 30 Mar 2023 none non-standard — Details →
1.7.33 31 Jan 2023 none non-standard — Details →
1.7.32 21 Nov 2022 none non-standard — Details →
1.7.31 19 Aug 2022 none non-standard — Details →
1.7.30 10 Jun 2022 none non-standard — Details →
1.7.29 23 May 2022 none non-standard — Details →
1.7.28 18 Dec 2021 none non-standard — Details →
1.7.27 03 Nov 2021 none non-standard — Details →
1.7.26 27 Oct 2021 none non-standard — Details →
1.7.25 30 Aug 2021 H1 non-standard Yes Details →
1.7.24 28 Jun 2021 none non-standard — Details →
1.7.23 28 May 2021 none non-standard — Details →
1.6.30 29 Apr 2021 none non-standard — Details →
1.7.22 13 Apr 2021 none non-standard — Details →
1.7.21 12 Apr 2021 none non-standard — Details →
1.7.20 19 Mar 2021 none non-standard — Details →
1.7.19 15 Jan 2021 none non-standard — Details →
1.7.18 20 Nov 2020 none non-standard — Details →
1.7.17 20 Oct 2020 none non-standard — Details →
1.7.16 14 Oct 2020 none non-standard — Details →
1.7.15 08 Oct 2020 none non-standard — Details →
1.7.14 24 Sep 2020 none non-standard — Details →
1.7.13 15 Sep 2020 none non-standard — Details →
1.7.12 24 Jul 2020 none non-standard — Details →
1.7.11 15 Apr 2020 none non-standard — Details →
1.6.29 15 Apr 2020 none non-standard — Details →
1.7.10 02 Apr 2020 none non-standard — Details →
1.7.9 20 Jan 2020 none non-standard — Details →
1.6.28 14 Jan 2020 none non-standard — Details →
1.7.8 05 Dec 2019 none non-standard — Details →
1.7.7 22 Oct 2019 none non-standard — Details →
1.7.6 05 Aug 2019 none non-standard — Details →
1.7.5 18 Jul 2019 none non-standard — Details →
1.7.4 28 Jun 2019 none non-standard — Details →
1.6.27 27 Jun 2019 none non-standard — Details →
1.7.3 23 May 2019 none non-standard — Details →
1.6.26 23 May 2019 none non-standard — Details →
1.7.2 29 Apr 2019 none non-standard — Details →
1.7.1 16 Apr 2019 none non-standard — Details →
1.6.25 09 Apr 2019 none non-standard — Details →
1.7.0 29 Mar 2019 none non-standard — Details →
1.6.24 27 Mar 2019 none non-standard — Details →
1.6.23 13 Mar 2019 none non-standard — Details →
1.6.22 25 Jan 2019 none non-standard — Details →
1.6.21 01 Nov 2018 none non-standard — Details →
1.6.20 31 Jul 2018 none non-standard — Details →
1.6.19 06 Apr 2018 none non-standard — Details →
1.6.18 05 Apr 2018 none non-standard — Details →
1.6.17 19 Sep 2017 none non-standard — Details →
1.6.16 02 Sep 2017 none non-standard — Details →
1.6.15 08 Aug 2017 none non-standard — Details →
1.6.14 16 Jun 2017 none non-standard — Details →
1.6.13 07 Jun 2017 none non-standard — Details →
1.6.12 22 Mar 2017 none non-standard — Details →
1.6.11 14 Mar 2017 none non-standard — Details →
1.6.10 13 Mar 2017 none non-standard — Details →
1.6.9 02 Mar 2017 none non-standard — Details →
1.6.8 21 Dec 2016 none non-standard — Details →
1.6.7 25 Nov 2016 none non-standard — Details →
1.6.6 13 Oct 2016 none non-standard — Details →
1.6.5 24 Sep 2016 none non-standard — Details →
1.6.4 30 Aug 2016 none non-standard — Details →
1.6.3 19 Aug 2016 none non-standard — Details →
1.6.2 05 Aug 2016 none non-standard — Details →
1.6.1 27 Jul 2016 none non-standard — Details →
1.6.0 15 Jul 2016 none non-standard — Details →
1.5.9 11 Jul 2016 none non-standard — Details →
1.5.8 17 Jun 2016 none non-standard — Details →
1.5.7 30 May 2016 none non-standard — Details →
1.5.6 22 Apr 2016 none non-standard — Details →
1.5.5 14 Apr 2016 none non-standard — Details →
1.5.4 22 Mar 2016 none non-standard — Details →
1.5.3 06 Nov 2015 none non-standard — Details →
1.5.2 15 Oct 2015 none — — Details →
1.5.1 14 Oct 2015 none — — Details →
1.5.0 01 Oct 2015 none — — Details →
1.4.7 01 Oct 2015 none — — Details →
1.4.6 29 Aug 2015 none — — Details →
1.4.5 24 Jul 2015 none — — Details →
1.4.4 23 Jul 2015 none — — Details →
1.4.3 27 May 2015 none — — Details →
1.4.2 06 May 2015 none — — Details →
1.4.1 14 Apr 2015 none — — Details →
1.3.4 04 Feb 2015 none — — Details →
1.3.3 28 Jan 2015 none — — Details →
1.3.2 27 Jan 2015 none — — Details →
1.3.1 13 Jan 2015 none — — Details →
1.3.0 10 Dec 2014 none — — Details →
1.2.2 24 Nov 2014 none — — Details →
1.2.1 22 Nov 2014 none — — Details →
1.2.0 17 Nov 2014 none — — Details →
1.1.1 05 Sep 2014 none — — Details →
1.1.0 03 Sep 2014 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 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 Hangfire.Core

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-41238: Hangfire.Core Missing Authorization with Default Settings in Dashboard UI 8.6 high 1.7.26 03 Nov 2021

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 Hangfire.Core

Is Hangfire.Core safe to use?

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

Vulert scores Hangfire.Core 86/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 Hangfire.Core affected?

No. 1.8.25, 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 Hangfire.Core should I use?

1.8.25 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 Hangfire.Core have?

1 vulnerability is recorded for Hangfire.Core 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 Hangfire.Core vulnerabilities disclosed?

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

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