Is Imageflow.Server 0.5 vulnerable?
NuGet · 10 releases from 0.5.0 to 0.5.10 · latest Imageflow.Server is 0.9.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. Imageflow.Server 0.5.10, the last 0.5 release, is affected by 1 known security advisory (1 high). Upgrade to 0.8.2 or later to fix all of them.
dotnet add package Imageflow.Server --version 0.8.2Is your project on an affected Imageflow.Server?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting Imageflow.Server 0.5.10
Imageflow affected by libwebp zero-day and should not be used with malicious source images.
- Affected
- <0.8.2
- Fixed in
- 0.8.2
Every Imageflow.Server 0.5.x release
Affected: 0.5.0 to 0.5.10. Latest Imageflow.Server: 0.9.0.
| Version | Known advisories |
|---|---|
| Imageflow.Server 0.5.10 | GHSA-7vpr-3ppw-qrpj |
| Imageflow.Server 0.5.9 | GHSA-7vpr-3ppw-qrpj |
| Imageflow.Server 0.5.8 | GHSA-7vpr-3ppw-qrpj |
| Imageflow.Server 0.5.7 | GHSA-7vpr-3ppw-qrpj |
| Imageflow.Server 0.5.6 | GHSA-7vpr-3ppw-qrpj |
| Imageflow.Server 0.5.5 | GHSA-7vpr-3ppw-qrpj |
| Imageflow.Server 0.5.3 | GHSA-7vpr-3ppw-qrpj |
| Imageflow.Server 0.5.2 | GHSA-7vpr-3ppw-qrpj |
| Imageflow.Server 0.5.1 | GHSA-7vpr-3ppw-qrpj |
| Imageflow.Server 0.5.0 | GHSA-7vpr-3ppw-qrpj |
Which of your client projects are still on Imageflow.Server 0.5?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact Imageflow.Server version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other Imageflow.Server versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.