Is CVE-2026-106113 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-106113 being exploited in the wild.

How severe is CVE-2026-106113?

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 to 4.1.1.

Is there a fix for CVE-2026-106113?

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-106113 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-106113?

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.

CVE-2026-106113: ImageSharp out-of-range access in histogram equalization

Q: Is there a fix for CVE-2026-106113?

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.

Q: How is CVE-2026-106113 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-106113?

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.

CVE-2026-106113 · Severity: high · CVSS 7.5 · Published 2026-10-06

ImageSharp is a .NET image processing library used to decode and manipulate images. When decoding specially crafted floating-point TIFF files and applying histogram equalization, a calculation error can produce invalid values that cause the application to crash, potentially disrupting services that process user-supplied images.

Technologies: SixLabors.ImageSharp (NuGet), SixLabors ImageSharp. Vendors: NuGet, SixLabors.

Quick answers

Is CVE-2026-106113 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-106113 being exploited in the wild.
How severe is CVE-2026-106113?: 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 to 4.1.1.
Is there a fix for CVE-2026-106113?: 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-106113 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-106113?: 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 32-bit floating-point TIFF decoded as Image<HalfVector4> can trigger non-finite or out-of-range luminance values in ColorNumerics.GetBT709Luminance. GrayscaleLevelsRowOperation.Invoke then uses this invalid value as an unchecked histogram offset, resulting in an out-of-bounds array access and process termination. The vulnerability affects HistogramEqualization but not Adaptive Histogram Equalization or AutoLevel.

Affected products

SixLabors ImageSharp 2.0.0 to 4.1.1

Identifiers

CVE-2026-106113
GHSA-j3p4-wp97-rph4

Timeline

2026-10-06: disclosed
2026-09-12: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.