ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-106113

ImageSharp: HistogramEqualization uses an unvalidated luminance as an unchecked histogram index

Published Oct 7, 2026 · catalog updated Oct 26, 2026 · ImageSharp: HistogramEqualization uses an

Last checked Oct 29, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-106113. EPSS is 0.39%. Act only if a listed version of ImageSharp: HistogramEqualization uses an is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (ImageSharp: HistogramEqualization uses an).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.39%
Remediation
Advisory link
Affected products
NuGet SixLabors.ImageSharp

### Summary can terminate a process when an application decodes an attacker-supplied 32-bit floating-point TIFF as and applies . An IEEE positive-infinity TIFF sample reaches a non-finite or otherwise out-of-range 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 only. It does not claim Adaptive Histogram Equalization or AutoLevel behavior. ### Affected package and versions - Package: (NuGet) - Affected range: - Commit 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 , while the finite control completes on each tested release. ### Details [ ](https://github.com/SixLabors/ImageSharp/blob/0815358f9202a78bc7f3b83e19282dc3654b500f/src/ImageSharp/Common/Helpers/ColorNumerics.cs#L24-L30) can produce a luminance that does not map to a valid histogram index. [ ](https://github.com/SixLabors/ImageSharp/blob/0815358f9202a78bc7f3b83e19282dc3654b500f/src/ImageSharp/Processing/Processors/Normalization/GrayscaleLevelsRowOperation%7BTPixel%7D.cs#L47-L62) then uses that result as an unchecked offset into the histogram. The reproduction reaches this code through the public extension. It does not test or claim the Adaptive Histogram Equalization or paths. ### Tested environment The reproduction uses the DLL in the published NuGet 4.1.1 package: ### Reproduction 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 . Observed result: The control is identical except samples are : When the same exploit binary was invoked through a shell inside the container, t

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • NuGet SixLabors.ImageSharp2.0.0 → 3.2.0
  • NuGet SixLabors.ImageSharp4.0.0 → 4.1.2

How to fix CVE-2026-106113

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-106113. EPSS is 0.39%. Act only if a listed version of ImageSharp: HistogramEqualization uses an is installed.

Which versions are affected?

Compare what you have installed with SixLabors.ImageSharp 2.0.0 → 3.2.0; SixLabors.ImageSharp 4.0.0 → 4.1.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-787: Out-of-bounds Write. EPSS 0.39%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 7, 2026 · GitHub Advisory Database

    Detected

    ### Summary can terminate a process when an application decodes an attacker-supplied 32-bit floating-point TIFF as and applies . An IEEE positive-infinity TIFF sample reaches a non-finite or otherwise out-of-range 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. Thi

  2. Oct 26, 2026 · GitHub Advisory Database

    Fix available

    SixLabors.ImageSharp fixed in 3.2.0; SixLabors.ImageSharp fixed in 4.1.2

  3. Oct 26, 2026 · GitHub Advisory Database

    Fix available

    SixLabors.ImageSharp fixed in 3.2.0

  4. Oct 26, 2026 · GitHub Advisory Database

    Fix available

    SixLabors.ImageSharp fixed in 4.1.2

  5. Oct 26, 2026 · GitHub Advisory Database

    Updated

    ### Summary can terminate a process when an application decodes an attacker-supplied 32-bit floating-point TIFF as and applies . An IEEE positive-infinity TIFF sample reaches a non-finite or otherwise out-of-range 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. Thi

Sources

References

Freshness

Last verified in this catalog Oct 26, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseOct 29, 2026
  • OpenSSF OSV / OSV ScannerOct 29, 2026
  • CVE.orgOct 27, 2026