ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-106114

ImageSharp: ICC CLUT parsing allocates from unvalidated channel and grid dimensions

Published Oct 7, 2026 · catalog updated Oct 26, 2026 · ImageSharp: ICC CLUT parsing

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-106114. EPSS is 0.33%. Act only if a listed version of ImageSharp: ICC CLUT parsing 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: ICC CLUT parsing).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.33%
Remediation
Advisory link
Affected products
NuGet SixLabors.ImageSharp

### Summary A malformed embedded ICC profile can make ImageSharp allocate memory from attacker-controlled CLUT channel and grid dimensions before verifying that the declared CLUT values are present. In published v1 through v3 packages, the public lazy ICC parser allocates approximately 115 MB from the 200-byte test profile before rejecting the truncated tag. In published v4 packages, decoding with ICC conversion enabled requests an 860,934,420-byte managed float array from the same profile. ### Affected package and versions - Package: (NuGet) - Affected range: - Commit corresponds to release **v4.1.1**. The parser defect is present from the first published NuGet prerelease, , through the latest published release, 4.1.1. The automatic conversion path used by the main PoC exists in ; earlier versions expose the same parser defect through the public accessor. ### Details The reproduced profile has an multi-process-elements ( ) tag with a element declaring 15 input channels, 15 output channels, and three grid points per input channel. [ ](https://github.com/SixLabors/ImageSharp/blob/0815358f9202a78bc7f3b83e19282dc3654b500f/src/ImageSharp/Metadata/Profiles/ICC/DataReader/IccDataReader.Lut.cs#L139-L162) computes and allocates that many floats before reading any CLUT values or verifying that the tag has enough remaining data. The supplied 200-byte profile ends immediately after the CLUT grid descriptor. In v4, the path is reached when an application decodes an embedded ICC profile using . The default setting, , does not parse the profile for conversion. In v1 through v3, uses a jagged representation. Loading an ICC-bearing JPEG and then accessing reaches the public lazy parser. The malformed profile allocates the -entry outer array before the missing CLUT values are detected. ### Reproduction environment and result The supplied automatic-conversion exploit and control were run against the published NuGet 4.1.1 DLL in Docker on Debian 12 / Linux arm64 with .NET SDK 8.0.424

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.ImageSharp1.0.0-beta0001 → 3.2.0
  • NuGet SixLabors.ImageSharp4.0.0 → 4.1.2

How to fix CVE-2026-106114

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-106114. EPSS is 0.33%. Act only if a listed version of ImageSharp: ICC CLUT parsing is installed.

Which versions are affected?

Compare what you have installed with SixLabors.ImageSharp 1.0.0-beta0001 → 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-789. EPSS 0.33%. 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 A malformed embedded ICC profile can make ImageSharp allocate memory from attacker-controlled CLUT channel and grid dimensions before verifying that the declared CLUT values are present. In published v1 through v3 packages, the public lazy ICC parser allocates approximately 115 MB from the 200-byte test profile before rejecting the truncated tag. In published v4 packages, decoding with

  2. Oct 26, 2026 · GitHub Advisory Database

    Fix available

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

  3. Oct 26, 2026 · GitHub Advisory Database

    Fix available

    SixLabors.ImageSharp fixed in 4.1.2

  4. Oct 26, 2026 · GitHub Advisory Database

    Fix available

    SixLabors.ImageSharp fixed in 3.2.0

  5. Oct 26, 2026 · GitHub Advisory Database

    Updated

    ### Summary A malformed embedded ICC profile can make ImageSharp allocate memory from attacker-controlled CLUT channel and grid dimensions before verifying that the declared CLUT values are present. In published v1 through v3 packages, the public lazy ICC parser allocates approximately 115 MB from the 200-byte test profile before rejecting the truncated tag. In published v4 packages, decoding with

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