Quick answers
- Is CVE-2026-106110 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106110 being exploited in the wild.
- How severe is CVE-2026-106110?
- High severity, with a CVSS score of 7.5, published 6 October 2026.
- Which products and versions are affected?
- SixLabors.ImageSharp (NuGet) >= 2.0.0, <= 4.1.1, ECOSYSTEM:introduced=2.0.0,fixed=4.1.2; SixLabors ImageSharp 2.0.0 through 4.1.1.
- Is there a fix for CVE-2026-106110?
- Yes. SixLabors.ImageSharp (NuGet): upgrade to 4.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106110 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106110?
- Check whether you run SixLabors.ImageSharp (NuGet) or SixLabors ImageSharp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- SixLabors.ImageSharp (NuGet): upgrade to 4.1.2 or later
dotnet add package SixLabors.ImageSharp --version 4.1.2
Technical details
A buffer overflow vulnerability exists in the TiffCcittCompressor initialization and T4BitCompressor.CompressStrip implementation when processing 1-bit TIFF images with CCITT Group 3 Fax compression. The vulnerable code fails to reserve sufficient space for row data and T4 end-of-line codes, leading to unchecked writes beyond the allocated output span. An attacker controlling the encode or decode-and-re-encode flow can trigger memory corruption or process termination.
Affected products
- SixLabors ImageSharp 2.0.0 through 4.1.1
Identifiers
- CVE-2026-106110
- GHSA-j9gm-c75j-xc9q
Timeline
- 2026-10-06: disclosed