ImageSharp: ICC LUT16 output channel count can write beyond Vector4

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-106112: 0.39% estimated exploitation activity in the next 30 days; percentile 32.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary When ICC conversion is enabled, a malformed embedded ICC LUT16 profile with more than four output channels can corrupt memory during ImageSharp color conversion. The ICC parser accepts up to 15 CLUT output channels, while the conversion implementation stores intermediate values in Vector4. Affected package and versions - Package: SixLabors.ImageSharp (NuGet) - Affected published releases: 4.0.0, 4.1.0, and 4.1.1 - Affected range: = 4.0.0, <= 4.1.1 - Commit 0815358f9202a78bc7f3b83e19282dc3654b500f corresponds to release v4.1.1. The reproduced ColorProfileHandling.Convert path and the unsafe Vector4 LUT operations are present in v4.0.0 and unchanged through v4.1.1. The three-output control succeeds on all three published 4.x releases; the fifteen-output exploit terminates all three. Details IccClut accepts one through fifteen input and output channels. In the reproduced A2B0 LUT16 path, an attacker-controlled profile declares three input channels and fifteen output channels.…

Published by the source

7 Oct 2026, 20:24 UTC

Last modified by the source

7 Oct 2026, 20:30 UTC

Source last checked

26 Oct 2026, 17:05 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-ffp7-56pq-64mr

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-ffp7-56pq-64mr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-106112

Advisory: ImageSharp: ICC LUT16 output channel count can write beyond Vector4
IDs: CVE-2026-106112, GHSA-ffp7-56pq-64mr
Record: https://patchnext.com/advisories/cve-2026-106112 (revision 2, source checked 26 Oct 2026, 17:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sixlabors.imagesharp 4.1.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet sixlabors.imagesharp: affected >= 4.0.0, <= 4.1.1; fixed in 4.1.2

## Suggested inspection (read-only)
- NuGet sixlabors.imagesharp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sixlabors.imagesharp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-ffp7-56pq-64mr (OSV record GHSA-ffp7-56pq-64mr lists affected ranges: NuGet sixlabors.imagesharp >=4.0.0 <4.1.2 (fixed))
- Verified: https://github.com/advisories/GHSA-ffp7-56pq-64mr (GitHub-reviewed advisory GHSA-ffp7-56pq-64mr lists affected ranges: NuGet sixlabors.imagesharp >=4.0.0 <=4.1.1)

Commands are suggestions: review each one before running it.