Is SixLabors.ImageSharp 1.0 vulnerable?

NuGet · 5 releases from 1.0.0 to 1.0.4 · latest SixLabors.ImageSharp is 4.1.3 · checked 18 Nov 2026

Yes: 8 known advisories

Yes. SixLabors.ImageSharp 1.0.4, the last 1.0 release, is affected by 8 known security advisories (3 high, 5 medium), including CVE-2025-27598, CVE-2024-41131, CVE-2024-27929. Upgrade to 3.2.0 or later to fix all of them.

Upgrade with:dotnet add package SixLabors.ImageSharp --version 3.2.0

Is your project on an affected SixLabors.ImageSharp?

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

Advisories affecting SixLabors.ImageSharp 1.0.4

  • MediumCVE-2026-106114GHSA-gwg2-r3hj-4w447 Oct 2026

    ImageSharp: ICC CLUT parsing allocates from unvalidated channel and grid dimensions

    Affected
    >=4.0.0 <4.1.2 · >=1.0.0-beta0001 <3.2.0
    Fixed in
    3.2.0, 4.1.2
  • MediumCVE-2025-54575GHSA-rxmq-m78w-7wmc30 Jul 2025

    SixLabors ImageSharp Has Infinite Loop in GIF Decoder When Skipping Malformed Comment Extension Blocks

    Affected
    <2.1.11 · >=3.0.0 <3.1.11
    Fixed in
    2.1.11, 3.1.11
  • HighCVE-2025-27598GHSA-2cmq-823j-5qj86 Mar 2025

    Out-of-bounds Write in SixLabors ImageSharp

    Affected
    >=3.0.0 <3.1.7 · <2.1.10
    Fixed in
    2.1.10, 3.1.7
  • MediumCVE-2024-41132GHSA-qxrv-gp6x-rc2322 Jul 2024

    SixLabors ImageSharp has Excessive Memory Allocation in Gif Decoder

    Affected
    <2.1.9 · >=3.0.0 <3.1.5
    Fixed in
    2.1.9, 3.1.5
  • HighCVE-2024-41131GHSA-63p8-c4ww-9cg722 Jul 2024

    SixLabors ImageSharp Out-of-bounds Write

    Affected
    <2.1.9 · >=3.0.0 <3.1.5
    Fixed in
    2.1.9, 3.1.5
  • MediumCVE-2024-32036GHSA-5x7m-6737-26cr15 Apr 2024

    SixLabors.ImageSharp vulnerable to data leakage

    Affected
    <2.1.8 · >=3.0.0 <3.1.4
    Fixed in
    2.1.8, 3.1.4
  • MediumCVE-2024-32035GHSA-g85r-6x2q-45w715 Apr 2024

    SixLabors.ImageSharp vulnerable to Memory Allocation with Excessive Size Value

    Affected
    <2.1.8 · >=3.0.0 <3.1.4
    Fixed in
    2.1.8, 3.1.4
  • HighCVE-2024-27929GHSA-65x7-c272-7g7r5 Mar 2024

    Use After Free in SixLabors.ImageSharp

    Affected
    >=3.0.0 <3.1.3 · <2.1.7
    Fixed in
    2.1.7, 3.1.3

Every SixLabors.ImageSharp 1.0.x release

Affected: 1.0.0 to 1.0.4. Latest SixLabors.ImageSharp: 4.1.3.

VersionKnown advisories
SixLabors.ImageSharp 1.0.4CVE-2026-106114, CVE-2025-54575, CVE-2025-27598, CVE-2024-41132, CVE-2024-41131, CVE-2024-32036, CVE-2024-32035, CVE-2024-27929
SixLabors.ImageSharp 1.0.3CVE-2026-106114, CVE-2025-54575, CVE-2025-27598, CVE-2024-41132, CVE-2024-41131, CVE-2024-32036, CVE-2024-32035, CVE-2024-27929
SixLabors.ImageSharp 1.0.2CVE-2026-106114, CVE-2025-54575, CVE-2025-27598, CVE-2024-41132, CVE-2024-41131, CVE-2024-32036, CVE-2024-32035, CVE-2024-27929
SixLabors.ImageSharp 1.0.1CVE-2026-106114, CVE-2025-54575, CVE-2025-27598, CVE-2024-41132, CVE-2024-41131, CVE-2024-32036, CVE-2024-32035, CVE-2024-27929
SixLabors.ImageSharp 1.0.0CVE-2026-106114, CVE-2025-54575, CVE-2025-27598, CVE-2024-41132, CVE-2024-41131, CVE-2024-32036, CVE-2024-32035, CVE-2024-27929

Which of your client projects are still on SixLabors.ImageSharp 1.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact SixLabors.ImageSharp version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other SixLabors.ImageSharp 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.