# CVE-2026-106114: ImageSharp: ICC CLUT parsing allocates from unvalidated channel and grid dimensions


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** ECHO-952c-9f86-5714, GHSA-gwg2-r3hj-4w44

## What is CVE-2026-106114?

CVE-2026-106114 is a medium-severity vulnerability in SixLabors ImageSharp, published on 6 Oct 2026. 

### Official description

ImageSharp is a 2D graphics library. From 1.0.0-beta0001 until 4.1.2, ICC CLUT parsing calculates allocation sizes from attacker-declared channel and grid dimensions before confirming that the profile contains the declared values. IccDataReader.ReadClutF32 can request a large float array, and earlier public IccProfile.Entries parsing paths can allocate a large jagged representation, from a short truncated profile. In version 4, automatic image conversion reaches the parser when DecoderOptions.ColorProfileHandling is Convert; the default Preserve mode avoids that conversion path. The demonstrated impact is memory pressure and input-validation failure, not unhandled process termination. This issue is fixed in version 4.1.2.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

## Which versions are affected by CVE-2026-106114?

4 open source packages ship an affected version, including SixLabors.ImageSharp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `SixLabors.ImageSharp` | NuGet | From 1.0.0-beta0001 | 3.2.0 |
| `SixLabors.ImageSharp` | NuGet | From 1.0.0-beta0001 | 3.2.0 |
| `SixLabors.ImageSharp` | NuGet | From 4.0.0 | 4.1.2 |
| `SixLabors.ImageSharp` | NuGet | From 4.0.0 | 4.1.2 |

Products: Sixlabors Imagesharp.

## How do I fix CVE-2026-106114?

Upgrade SixLabors.ImageSharp to a fixed version for your release line: 3.2.0 or 4.1.2.

## Is CVE-2026-106114 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-106114 exists.

## Other vulnerabilities in SixLabors ImageSharp

- [CVE-2026-106110](https://insights.sbomify.com/CVE-2026-106110/): ImageSharp: TIFF CCITT T4 encoder can write past its compressed output buffer (high 7.5)
- [CVE-2026-106112](https://insights.sbomify.com/CVE-2026-106112/): ImageSharp: ICC LUT16 output channel count can write beyond Vector4 (high 7.5)
- [CVE-2026-106113](https://insights.sbomify.com/CVE-2026-106113/): ImageSharp: HistogramEqualization uses an unvalidated luminance as an unchecked histogram index (high 7.5)
- [CVE-2026-106115](https://insights.sbomify.com/CVE-2026-106115/): ImageSharp: TIFF CCITT T6 encoder writes beyond an undersized output buffer (high 7.5)
- [CVE-2026-106117](https://insights.sbomify.com/CVE-2026-106117/): ImageSharp: CCITT fax decompression (T4/Modified Huffman): unbounded WriteBits overflows strip buffer — heap OOB write in SixLabors.ImageSharp (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106114 and fix it if it is affected.

What it is: CVE-2026-106114 is a medium-severity vulnerability in SixLabors ImageSharp, published on 6 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-106114 exists.

Affected packages and fixed versions:
- SixLabors.ImageSharp (NuGet): affected from 1.0.0-beta0001; fixed in 3.2.0
- SixLabors.ImageSharp (NuGet): affected from 1.0.0-beta0001; fixed in 3.2.0
- SixLabors.ImageSharp (NuGet): affected from 4.0.0; fixed in 4.1.2
- SixLabors.ImageSharp (NuGet): affected from 4.0.0; fixed in 4.1.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-106114/ (Markdown: https://insights.sbomify.com/CVE-2026-106114/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106114
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106114
- OSV: https://osv.dev/vulnerability/CVE-2026-106114

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-106114/
Summaries are generated and may contain mistakes; the official description above is the record.