Hangfire.Core vulnerabilities
An easy and reliable way to perform fire-and-forget, delayed and recurring, long-running, short-running, CPU or I/O intensive tasks in .NET applications. No Windows Service / Task Scheduler required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. https://www.hangfire.io/
- Registry
- NuGet
- Latest
- 1.8.25
1 known advisory
The latest version, 1.8.25, is not affected by any of them. Projects on older versions may be.
dotnet add package Hangfire.Core --version 1.8.25Is your project on an affected Hangfire.Core?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for Hangfire.Core
Missing Authorization with Default Settings in Dashboard UI
- Affected
- >=1.7.25 <1.7.26
- Fixed in
- 1.7.26
Is your Hangfire.Core version vulnerable?
- Hangfire.Core 1.8No known advisories in 1.8.25
- Hangfire.Core 1.7No known advisories in 1.7.37
- Hangfire.Core 1.6No known advisories in 1.6.30
- Hangfire.Core 1.5No known advisories in 1.5.9
- Hangfire.Core 1.4No known advisories in 1.4.7
- Hangfire.Core 1.3No known advisories in 1.3.4
- Hangfire.Core 0.9No known advisories in 0.9.1
- Hangfire.Core 0.8No known advisories in 0.8.3
- Hangfire.Core 0.7No known advisories in 0.7.5
- Hangfire.Core 0.6No known advisories in 0.6.2
- Hangfire.Core 0.5No known advisories in 0.5.2
Which of your client projects still run an old Hangfire.Core?
NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other NuGet packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.