Skip to main content

SixLabors ImageSharp EUVDEUVD-2026-93553

| CVE-2026-106112 HIGH
Out-of-bounds Write (CWE-787)
2026-10-06 GitHub_M GHSA-ffp7-56pq-64mr
7.5
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Upload image with malformed ICC profile
  2. Delivery
    LUT16 declares >4 output channels
  3. Exploit
    Interpolation writes past Vector4 destination
  4. Execution
    Heap/stack memory corrupted
  5. Impact
    Process terminates (DoS)

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the application to have explicitly set DecoderOptions.ColorProfileHandling to Convert; the default Preserve mode does not invoke ICC conversion and is not vulnerable. The attacker must supply an image containing a malformed embedded ICC profile whose LUT16 transform (processed by ClutCalculator.Calculate or LutEntryCalculator.CalculateLut) declares more than four input/output channels or tone-response curves, causing writes beyond the four-float Vector4 destination. Affected versions are 4.0.0 through 4.1.1; the primary limiting factor is the non-default Convert configuration, which significantly reduces the exposed population despite the unauthenticated network vector.

Impact

This is a memory-corruption (CWE-787, out-of-bounds write) flaw in SixLabors ImageSharp that the vendor advisory (GHSA-ffp7-56pq-64mr) and the fixing PR #3187 confirm. The NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) indicates network-reachable, unauthenticated, low-complexity exploitation with impact limited to availability - consistent with the description, which states the overflow 'can corrupt memory and terminate the process' rather than achieve code execution or data disclosure. No EPSS score, KEV listing, or POC was provided in the input, so exploitation probability cannot be quantified and there is no public exploit identified at time of analysis. The single most important mitigating signal is NOT reflected in the CVSS score: the code path only runs when DecoderOptions.ColorProfileHandling is explicitly set to Convert; the default Preserve mode does not run ICC conversion and is unaffected. This materially narrows real-world exposure to the subset of applications that opt into color conversion, making this a conditional availability/DoS issue rather than a broadly exploitable critical flaw. Treat as medium-priority patch urgency for deployments known to use Convert mode, lower otherwise.

Exploit ScenarioDerived

An application using ImageSharp 4.0.0-4.1.1 with DecoderOptions.ColorProfileHandling=Convert accepts user-supplied images (e.g., an upload/thumbnail service). An attacker submits an image with a malformed embedded ICC profile whose LUT16 transform declares more than four output channels, causing ClutCalculator/LutEntryCalculator to write beyond the four-float Vector4 destination, corrupting memory and crashing the worker process. No public exploit code was identified; impact is denial of service, not confirmed code execution.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

Memory corruption in SixLabors ImageSharp 4.0.0 through 4.1.1 allows an unauthenticated remote attacker to crash or destabilize a host process by supplying an image whose embedded ICC profile declares more than four LUT16 input/output channels, causing out-of-bounds writes past a four-float internal buffer. The flaw is only reachable when an application has explicitly set DecoderOptions.ColorProfileHandling to Convert, since the default Preserve mode does not run ICC conversion; the independent assessment scores it CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), reflecting an availability-only impact rather than data disclosure or modification. No public exploit code was identified at time of analysis, and the issue is fixed in version 4.1.2.

RemediationAI

Vendor-released patch: ImageSharp 4.1.2 - upgrade the SixLabors.ImageSharp package to 4.1.2 or later and rebuild, as documented in GHSA-ffp7-56pq-64mr (https://github.com/SixLabors/ImageSharp/security/advisories/GHSA-ffp7-56pq-64mr), PR https://github.com/SixLabors/ImageSharp/pull/3187, commit b03f0ed7e5be760eecc740fa53dd166b18ae9b23, and release https://github.com/SixLabors/ImageSharp/releases/tag/v4.1.2. If an immediate upgrade is not possible, the most effective compensating control is to stop invoking the vulnerable code path entirely by leaving DecoderOptions.ColorProfileHandling at - or explicitly setting it back to - the default Preserve value, which disables ICC conversion; the trade-off is that embedded profiles are no longer applied, so images may render with inaccurate colors on calibrated or wide-gamut workflows. Additionally, treat image decoding as hostile input: run decoding in a low-privilege, resource-capped worker process or sandbox so any memory corruption or process termination is contained rather than affecting the primary service, and reject or re-encode uploaded images with a defensive sanitizer before they reach ICC-aware processing. Note that no public exploit code was identified at time of analysis, so the priority is determined by whether Convert mode is actually enabled in your deployment; audit for DecoderOptions.ColorProfileHandling usage to establish exposure before scheduling the upgrade.

Affected VersionsENISA

ImageSharp 4.0.0, < 4.1.2

Affected Packages

nuget sixlabors.imagesharp fix: 4.1.2
euvd imagesharp_4_0_0 fix: 4.1.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in nuget, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

ImageSharp is a cross-platform .NET 2D graphics library, and this issue lives in its ICC color-profile processing pipeline. When a profile is applied, ClutCalculator.Calculate and LutEntryCalculator.CalculateLut interpolate color-lookup-table (CLUT) and tone-response-curve data, but the implementation stores intermediate and final values in System.Numerics.Vector4 - a fixed four-float (16-byte) destination. A LUT16 tag in a malformed embedded profile can legally declare more than four input or output channels, and the code performed no bounds check on that declared count, so it wrote one additional float per extra channel, an out-of-bounds write of class CWE-787 (the vendor's patch also guards TrcCalculator's entry count). The fix, delivered through PR #3187 and the v4.1.2 release, adds explicit InputChannelCount/OutputChannelCount and TRC entry-count checks that throw InvalidIccProfileException instead of writing past the vector, and it introduces BufferedReadStreamExtensions (IsReadRangeValid/TryGetReadLength/Skip) with overflow-safe range validation so untrusted declared lengths cannot wrap or exceed the stream. The vulnerable path is gated behind DecoderOptions.ColorProfileHandling = Convert; the default Preserve mode never executes ICC conversion, which is the primary factor limiting the exposed population despite the network-reachable, unauthenticated trigger.

Know when Imagesharp gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 7.5 HIGH

A crafted image reliably triggers the overflow against a Convert-configured service with no auth or user interaction (AV:N/AC:L/PR:N/UI:N); impact is process crash only, so C:N/I:N/A:H.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

2
Patch available
Oct 06, 2026 - 19:04 EUVD
CVE Published
Oct 06, 2026 - 17:45 cve.org
HIGH 7.5

DescriptionCVE.org

ImageSharp is a 2D graphics library. From 4.0.0 until 4.1.2, ICC LUT16 conversion accepts more than four output channels even though ClutCalculator.Calculate and LutEntryCalculator.CalculateLut store intermediate and output values in Vector4. When DecoderOptions.ColorProfileHandling is set to Convert, a malformed embedded profile can direct interpolation and output-LUT operations to write one float per declared channel beyond the four-float destination. This can corrupt memory and terminate the process; the default Preserve mode does not run ICC conversion. This issue is fixed in version 4.1.2.

Technical POC Analysis

Out-of-bounds write (CWE-787) in the ICC LUT16 conversion path of SixLabors.ImageSharp (NuGet).

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

SixLabors ImageSharp versions 4.0.0 through 4.1.1 are vulnerable to a memory corruption issue that could allow an unauthenticated remote attacker to crash or destabilize a host process when processing a malicious image, but only if the application has enabled the non-default ICC color conversion mode. This availability-only flaw could disrupt business services for organizations that handle untrusted images with that configuration, and while there is no public exploit identified at time of analysis, the potential for denial-of-service makes it a priority. Leadership should direct remediation efforts to upgrade to version 4.1.2 or disable the vulnerable conversion setting.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 73% exploitable
Prevalence
High
one of the most widely used .NET image-processing libraries
Threat Intel
1
1 source
Data Quality
5 sources
Confidence: Medium
EUVD NVD CVE.org EPSS Vulnrichment GHSA GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

CVE-2025-27598 HIGH POC
7.5 Mar 06

ImageSharp is a 2D graphics API. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authenti

CVE-2024-27929 HIGH POC
7.1 Mar 05

ImageSharp is a managed, cross-platform, 2D graphics library. Rated high severity (CVSS 7.1), this vulnerability is no a

CVE-2026-106115 HIGH
7.5 Oct 06

Out-of-bounds heap writes in the ImageSharp TIFF CCITT Group 4 (T6) fax encoder, affecting versions 2.1.0 through 4.1.1,

CVE-2026-106113 HIGH
7.5 Oct 06

Denial of service in SixLabors ImageSharp (2.0.0 up to but not including 4.1.2) lets a remote, unauthenticated attacker

CVE-2026-106110 HIGH
7.5 Oct 06

TIFF encoding in SixLabors ImageSharp 2.0.0 through 4.1.1 can write past the end of an undersized compressed-data buffer

CVE-2026-106118 HIGH
7.5 Oct 06

Heap corruption and process termination in SixLabors ImageSharp 3.0.0 through 4.1.0 can be triggered by decoding a craft

CVE-2026-106117 HIGH
7.5 Oct 06

Heap buffer overflow in SixLabors ImageSharp (all versions from 3.0.0 up to but excluding 4.1.1) is triggered when the l

CVE-2024-41132 HIGH
7.5 Jul 22

ImageSharp is a 2D graphics API. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authenti

CVE-2024-41131 HIGH
7.5 Jul 22

ImageSharp is a 2D graphics API. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authenti

CVE-2024-32036 MEDIUM
6.5 Apr 15

ImageSharp is a 2D graphics API. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authen

CVE-2024-32035 MEDIUM
6.5 Apr 15

ImageSharp is a 2D graphics API. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authen

CVE-2026-106111 MEDIUM
5.9 Oct 06

Information disclosure in SixLabors ImageSharp 4.0.0 through 4.1.1 allows an attacker who supplies a crafted OpenEXR ima

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy