Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessUpload crafted tiled CCITT TIFF to decoder
-
DeliveryDecompressor sized to frame width, buffer sized to tile width
-
ExploitFrame-width scanline written into tile-width buffer
-
ExecutionOut-of-bounds heap write corrupts memory
-
ImpactProcess terminates (denial of service)
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 target application to decode an attacker-supplied TIFF that is (1) tiled and (2) uses CCITT fax compression - specifically T4, T6, or Modified Huffman - with (3) a TileWidth strictly smaller than ImageWidth; this mismatch is the precise trigger because TiffDecoderCore sizes the destination buffer by TileWidth while TiffDecompressorsFactory.Create constructs the decompressor with the full frame width. Limiting factors: the strip-decoding path is unaffected (this is a distinct tiled-path bug), and the application must actually invoke TIFF decoding on untrusted input. No authentication or user interaction is required per the CVSS vector (PR:N/UI:N), and no special configuration is needed beyond accepting and decoding untrusted images on a vulnerable version (3.0.0-4.1.0). |
| Impact | The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) describes a remotely reachable, low-complexity, unauthenticated flaw whose scored impact is availability-only (A:H) - a denial-of-service via process termination, consistent with CWE-787 heap corruption. A tension worth flagging: the description asserts 'attacker-controlled out-of-bounds writes' and 'heap corruption', which could in principle enable memory-safety abuse beyond a crash, yet the official vector rates C:N/I:N, so confidentiality/integrity impact (and any code-execution path) is NOT confirmed and should not be assumed. No EPSS score was provided, so exploitation probability cannot be quantified. The CVE is not listed in CISA KEV and no public exploit code was supplied - the GitHub links are the vendor fix (remediation), not a weaponized POC. Overall this is a legitimate, easily-reachable DoS in image-upload pipelines rather than a confirmed RCE; priority is moderate-to-high for services that decode untrusted TIFFs, but the elevated CVSS reflects availability impact, not demonstrated system compromise. |
| Exploit ScenarioDerived | An application that uses ImageSharp (3.0.0-4.1.0) to decode user-supplied images receives a crafted tiled TIFF whose TileWidth is smaller than ImageWidth and which uses CCITT fax compression (T4/T6/Modified Huffman). During tiled decoding, frame-width fax scanlines are directed into the smaller tile-width destination buffer, triggering attacker-controlled out-of-bounds heap writes that corrupt memory and terminate the process. No public exploit code exists at time of analysis; only the vendor patch is published. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Heap corruption and process termination in SixLabors ImageSharp 3.0.0 through 4.1.0 can be triggered by decoding a crafted tiled TIFF that uses CCITT fax compression (T4, T6, or Modified Huffman) with a TileWidth smaller than ImageWidth. Because DestinationBuffer is sized by TileWidth while TiffDecompressorsFactory.Create instantiates the fax decompressor with the full frame width, attacker-controlled scanlines overflow the tile buffer, producing out-of-bounds writes and CWE-787 heap corruption. The flaw is remotely reachable, requires no authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5), and is scored availability-only. No public exploit code has been identified at time of analysis, and the issue is fixed in version 4.1.1.
RemediationAI
Vendor-released patch: upgrade ImageSharp to version 4.1.1, which is the first release containing the fix (https://github.com/SixLabors/ImageSharp/releases/tag/v4.1.1), cherry-picking the change from pull request 3176 or commit 9ee7d1dd5b62d8c9f16cc755e76828386bc2191f if you maintain a fork. The patch passes the tile row width (faxWidth) into T4, T6, and Modified Huffman decompressors and adds a guard that rejects any decoded run exceeding the remaining row width before the unchecked bit writer is reached; review the advisory at https://github.com/SixLabors/ImageSharp/security/advisories/GHSA-v76p-62qx-wwq2 for details. If immediate upgrading is not possible, compensating controls include rejecting or quarantining tiled TIFFs that declare CCITT fax compression (T4/T6/Modified Huffman) until TileWidth can be validated against ImageWidth, since any such file where TileWidth is smaller than ImageWidth is a potential trigger; the trade-off is loss of legitimate tiled fax-compressed TIFF support. Alternatively, route TIFF decoding through an isolated low-privilege worker process with strict memory limits so that heap corruption terminates only the sandboxed decoder rather than the parent application, accepting added architectural complexity and reduced throughput, or disable TIFF decoding on untrusted input entirely if the format is not business-critical. Any compensating control short of the 4.1.1 patch leaves the underlying unchecked write reachable.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in nuget
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability lives in the TIFF decoder of the ImageSharp 2D graphics library and belongs to the CWE-787 (out-of-bounds write) class. TIFF permits tiled image organization, where the image is divided into rectangular tiles whose dimensions are declared in the TileWidth and TileLength tags. ImageSharp sizes the destination buffer for a tile using TileWidth, but TiffDecompressorsFactory.Create historically constructed the fax decompressors (T4TiffCompression, T6TiffCompression, and ModifiedHuffmanTiffCompression) using the full frame width rather than the tile width. When CCITT Group 3 (T4), Group 4 (T6), or Modified Huffman compression is used on a tiled image and TileWidth is strictly less than ImageWidth, TiffDecoderCore.DecodeTilesChunky feeds frame-width fax scanlines into a tile-width buffer. The bit writer performs unchecked writes and the pre-existing width check only validated pixelsWritten after the fact, so a legal per-row run code that decodes more pixels than the tile width causes an attacker-controlled out-of-bounds write. This is distinct from oversized CCITT run handling in the strip-decoding path, which is unaffected. The upstream fix passes faxWidth (= tileWidth when tiled, otherwise width) into the decompressors and adds an explicit guard rejecting any decoded run whose RunLength exceeds the remaining row width before the unchecked bit writer is invoked. The affected CPE range is cpe:2.3:a:sixlabors:imagesharp:*:*:*:*:*:*:*:*.
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
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Untrusted image reaches the decoder remotely with no auth or interaction (AV:N/AC:L/PR:N/UI:N); demonstrable impact is a crash, so A:H with C:N/I:N since memory disclosure or integrity abuse is unproven.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
ImageSharp is a 2D graphics library. From 3.0.0 until 4.1.1, tiled TIFF decoding allocates a destination buffer using TileWidth but TiffDecompressorsFactory.Create constructs T4, T6, and Modified Huffman decompressors using the full frame width. TiffDecoderCore.DecodeTilesChunky can therefore direct frame-width fax scanlines into a tile-width buffer when TileWidth is smaller than ImageWidth. The mismatch causes attacker-controlled out-of-bounds writes, heap corruption, and process termination even with legal per-row run codes. This tiled-path vulnerability is distinct from oversized CCITT runs in strip decoding. This issue is fixed in version 4.1.1.
Technical POC Analysis
CWE-787 (out-of-bounds write), caused by a width mismatch between tile buffer allocation and the CCITT fax decompressor.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
A heap-corruption flaw in the SixLabors ImageSharp library (versions 3.0.0 through 4.1.0) allows any unauthenticated remote party to crash or destabilize services that decode TIFF images, simply by submitting a specially crafted tiled CCITT-fax TIFF file. Because ImageSharp is embedded in a wide range of .NET web applications, content pipelines, and document-processing services, the practical exposure is broad: affected business functions include any customer-facing upload, document conversion, or media-ingestion workflow. The impact is availability-focused rather than data-theft, but an outage in a shared image-processing component can cascade across multiple products simultaneously.
Apply vendor patch (upgrade to SixLabors.ImageSharp 4.1.1 or later). If upgrading is not immediately possible, disable persistent image processing for TIFF: reject TIFF uploads at the perimeter or disable TIFF decoding entirely for untrusted input, run TIFF decoding in an isolated low-privilege sandboxed worker with CPU/memory limits and automatic restart, and rate-limit or queue image-processing requests to contain the blast radius of a crash.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
More in Imagesharp
View allImageSharp is a 2D graphics API. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authenti
ImageSharp is a managed, cross-platform, 2D graphics library. Rated high severity (CVSS 7.1), this vulnerability is no a
Out-of-bounds heap writes in the ImageSharp TIFF CCITT Group 4 (T6) fax encoder, affecting versions 2.1.0 through 4.1.1,
Denial of service in SixLabors ImageSharp (2.0.0 up to but not including 4.1.2) lets a remote, unauthenticated attacker
TIFF encoding in SixLabors ImageSharp 2.0.0 through 4.1.1 can write past the end of an undersized compressed-data buffer
Heap buffer overflow in SixLabors ImageSharp (all versions from 3.0.0 up to but excluding 4.1.1) is triggered when the l
Memory corruption in SixLabors ImageSharp 4.0.0 through 4.1.1 allows an unauthenticated remote attacker to crash or dest
ImageSharp is a 2D graphics API. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authenti
ImageSharp is a 2D graphics API. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authenti
ImageSharp is a 2D graphics API. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authen
ImageSharp is a 2D graphics API. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authen
Information disclosure in SixLabors ImageSharp 4.0.0 through 4.1.1 allows an attacker who supplies a crafted OpenEXR ima
EUVD-2026-93770
GHSA-v76p-62qx-wwq2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB