Is SixLabors.ImageSharp 2.0 vulnerable?
NuGet · 1 release from 2.0.0 to 2.0.0 · latest SixLabors.ImageSharp is 4.1.3 · checked 18 Nov 2026
Yes: 11 known advisories
Yes. SixLabors.ImageSharp 2.0.0, the last 2.0 release, is affected by 11 known security advisories (5 high, 6 medium), including CVE-2026-106110, CVE-2026-106113, CVE-2025-27598. Upgrade to 3.2.0 or later to fix all of them.
dotnet add package SixLabors.ImageSharp --version 3.2.0Is your project on an affected SixLabors.ImageSharp?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting SixLabors.ImageSharp 2.0.0
ImageSharp: BigTIFF IFD count can keep a decoder thread in a non-progressing loop
- Affected
- >=2.0.0 <3.2.0 · >=4.0.0 <4.1.2
- Fixed in
- 3.2.0, 4.1.2
ImageSharp: TIFF CCITT T4 encoder can write past its compressed output buffer
- Affected
- >=2.0.0 <3.2.0 · >=4.0.0 <4.1.2
- Fixed in
- 3.2.0, 4.1.2
ImageSharp: HistogramEqualization uses an unvalidated luminance as an unchecked histogram index
- Affected
- >=2.0.0 <3.2.0 · >=4.0.0 <4.1.2
- Fixed in
- 3.2.0, 4.1.2
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
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
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
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
SixLabors ImageSharp Out-of-bounds Write
- Affected
- <2.1.9 · >=3.0.0 <3.1.5
- Fixed in
- 2.1.9, 3.1.5
SixLabors.ImageSharp vulnerable to data leakage
- Affected
- <2.1.8 · >=3.0.0 <3.1.4
- Fixed in
- 2.1.8, 3.1.4
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
Use After Free in SixLabors.ImageSharp
- Affected
- >=3.0.0 <3.1.3 · <2.1.7
- Fixed in
- 2.1.7, 3.1.3
Which of your client projects are still on SixLabors.ImageSharp 2.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.