Is Imageflow.Server 0.8 vulnerable?

NuGet · 4 releases from 0.8.0 to 0.8.3 · latest Imageflow.Server is 0.9.0 · checked 18 Nov 2026

No known advisories in the last release

Imageflow.Server 0.8.3, the last 0.8 release, has no known advisories. 1 advisory affects earlier 0.8.x releases, so update to 0.8.3.

Update within 0.8:dotnet add package Imageflow.Server --version 0.8.3

Is your project on an affected Imageflow.Server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 0.8.x, affecting earlier releases

  • HighGHSA-7vpr-3ppw-qrpj27 Sept 2023

    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.8.x release

Affected: 0.8.0 to 0.8.1. 0.8.2 and later are not affected. Latest Imageflow.Server: 0.9.0.

VersionKnown advisories
Imageflow.Server 0.8.3None
Imageflow.Server 0.8.2None
Imageflow.Server 0.8.1GHSA-7vpr-3ppw-qrpj
Imageflow.Server 0.8.0GHSA-7vpr-3ppw-qrpj

Which of your client projects are still on Imageflow.Server 0.8?

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.