Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessUpload crafted one-bit CCITTG4 TIFF
-
DeliveryApp decodes attacker input
-
ExploitRe-encode inherits G4+one-bit metadata
-
ExecutionT6 compressor overflows strip buffer
-
PersistUnchecked WriteCode out-of-bounds write
-
ImpactMemory corruption crashes process
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 | Requires the host application (using SixLabors ImageSharp 2.1.0 through 4.1.1) to run a decode-and-re-encode flow on attacker-supplied images where TiffCompression.CcittGroup4Fax and one-bit (bilevel) metadata are inherited from the input, so the TIFF CCITT Group 4 (T6) encoder path is reached. The under-allocation is Width×rowsPerStrip bytes, overflowed by encoded row data plus two 12-bit end-of-facsimile-block codes. Limiting factors: the application must actually re-encode images to TIFF G4 (not merely decode or display them); impact is confined to availability (process termination), with no confidentiality or integrity effect; versions 4.1.2 and later are not affected. |
| Impact | This is a genuine but bounded availability (DoS) issue rather than a critical code-execution priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) reflects a remotely reachable, unauthenticated, low-complexity flaw whose only impact is availability - the out-of-bounds write corrupts memory and terminates the process, with C:N/I:N meaning no confirmed confidentiality or integrity loss. Although CWE-787 (out-of-bounds write) can sometimes enable code execution, the vendor advisory and description scope the realistic outcome to memory corruption and process crash, and the CVSS explicitly rates C/I as none; do NOT assume RCE from the CWE alone. No EPSS score, CISA KEV listing, or public POC was provided, so exploitation status is 'no public exploit identified at time of analysis' - there is no evidence of active exploitation or weaponization. A key limiting factor tempers the AV:N/AC:L signal: exploitation requires the host application to perform a decode-and-re-encode flow that inherits TIFF CcittGroup4Fax compression and one-bit metadata from attacker input, which is a narrower condition than the raw vector implies. Verdict: patch in routine cycles - real and remotely triggerable, but availability-only and dependent on a specific re-encode code path. |
| Exploit ScenarioDerived | An attacker uploads a crafted one-bit TIFF image with CCITT Group 4 (T6) fax compression to a .NET web service that uses ImageSharp (2.1.0-4.1.1) to decode and re-encode user images. During re-encode, T6BitCompressor.CompressStrip emits encoded rows plus two 12-bit end-of-facsimile-block codes beyond the under-allocated Width×rowsPerStrip buffer, and TiffCcittCompressor.WriteCode's unchecked writes corrupt memory and crash the process. No public exploit code is identified, but the attack requires no authentication or user interaction once such a re-encode flow is exposed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Out-of-bounds heap writes in the ImageSharp TIFF CCITT Group 4 (T6) fax encoder, affecting versions 2.1.0 through 4.1.1, allow attacker-supplied image data to corrupt memory and terminate the process. The encoder allocates only Width × rowsPerStrip bytes for a strip while T6BitCompressor.CompressStrip can emit encoded row data plus two 12-bit end-of-facsimile-block codes beyond that capacity, and TiffCcittCompressor.WriteCode performs the writes without bounds checks; a decode-and-re-encode flow that inherits TiffCompression.CcittGroup4Fax and one-bit bilevel metadata from the input reaches this path, giving unauthenticated remote attackers a denial-of-service primitive (CVSS 7.5, AV:N/AC:L/PR:N/UI:N, C:N/I:N/A:H). Impact is confined to availability - no confidentiality or integrity effect - and there is no public exploit code identified at time of analysis and no CISA KEV listing; the issue is fixed in version 4.1.2.
RemediationAI
Vendor-released patch: upgrade SixLabors.ImageSharp to 4.1.2 or later (https://github.com/SixLabors/ImageSharp/releases/tag/v4.1.2), which contains the bounds-checking fix from commit a9498c6db3642ef92c712ebc81e706914ac16a95 and PR https://github.com/SixLabors/ImageSharp/pull/3187; see advisory GHSA-jjfr-hcj7-qf5w. Where an immediate upgrade is not possible, the most effective compensating control is to break the decode-and-re-encode inheritance chain: after decoding, explicitly force the output TIFF encoder's compression to a scheme other than CcittGroup4Fax (for example LZW, Deflate, or PackBits) instead of allowing the encoder to inherit the input's TiffCompression setting, and reject or down-convert one-bit bilevel images before re-encoding - the trade-off is larger output files and a change in downstream format expectations for fax/G4 workflows. Alternatively, validate and re-author TIFF metadata (dimensions, rows-per-strip, bit depth) before re-encoding so attacker-controlled strip geometry never reaches the encoder, accepting that legitimate multi-page G4 fax documents may need special-casing. Because exploitation requires the host application to actually re-encode attacker-supplied images, run such processing in an isolated worker process, container, or sandbox with memory and restart limits so a corrupted heap results in a contained process termination rather than host compromise - this does not remove the bug and only limits blast radius. Decode-only pipelines (thumbnailing, format conversion away from TIFF G4) can be treated as lower priority but should still be patched on the normal cycle.
Affected VersionsENISA
Affected Packages
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 SixLabors' managed 2D graphics library for .NET, exposed via the CPE cpe:2.3:a:sixlabors:imagesharp (all versions up to the 4.1.2 fix). The root cause is CWE-787 (out-of-bounds write) in the TIFF CCITT Group 4 / T.6 fax codec: the encoder sizes a strip buffer as Width multiplied by rowsPerStrip, but the T6 compressor can legitimately emit more bytes than that - encoded row data plus two 12-bit end-of-facsimile-block (EFB) termination codes - and TiffCcittCompressor.WriteCode writes these without validating remaining capacity. Because TIFF compression scheme and bilevel (one-bit) pixel depth are metadata fields carried by the decoded image object, a decode-and-re-encode pipeline can inherit TiffCompression.CcittGroup4Fax from an untrusted source file and drive the vulnerable encoder with attacker-influenced dimensions and row counts. The upstream fix in PR #3187 additionally hardened several adjacent parsing surfaces, adding channel-count limits to the ICC ICC profile calculators (ClutCalculator, LutEntryCalculator, TrcCalculator, which now reject profiles with more than four input/output channels, tone-response curves, or LUT entries) and introducing a BufferedReadStreamExtensions helper that validates read ranges (IsReadRangeValid/TryGetReadLength) to prevent offset-plus-length integer overflow and under-allocation when consuming declared lengths. Note that the assessed impact is availability-only per the CVSS vector (S:U/C:N/I:N/A:H) even though the underlying memory-safety class can theoretically corrupt adjacent heap data.
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
Crafted image is processed by a network-reachable, unauthenticated re-encode flow with low complexity; the out-of-bounds write only crashes the process, so impact is availability-only.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
ImageSharp is a 2D graphics library. From 2.1.0 until 4.1.2, the TIFF CCITT Group 4 encoder allocates Width times rowsPerStrip bytes even though T6BitCompressor.CompressStrip can emit encoded row data and two 12-bit end-of-facsimile-block codes beyond that capacity. TiffCcittCompressor.WriteCode performs unchecked writes, and a decode-and-re-encode flow can inherit TiffCompression.CcittGroup4Fax and one-bit metadata from attacker-supplied input. The resulting out-of-bounds writes can corrupt memory and terminate the process. This issue is fixed in version 4.1.2.
Technical POC Analysis
CWE-787 (Out-of-bounds Write) in the TIFF CCITT Group 4 (T6) encoder of SixLabors.ImageSharp.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
ImageSharp's TIFF CCITT Group 4 (T6) fax encoder, versions 2.1.0 through 4.1.1, contains an out-of-bounds heap write that unauthenticated remote attackers can trigger via crafted TIFF images, causing process termination and denial of service. Organizations that process untrusted TIFF files with this library face service disruptions affecting image processing availability, though confidentiality and integrity remain intact. Leadership should prioritize remediation because the flaw is remotely exploitable without authentication and affects a widely used image processing component.
Apply vendor patch.
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
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 corruption and process termination in SixLabors ImageSharp 3.0.0 through 4.1.0 can be triggered by decoding a craft
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-93557
GHSA-jjfr-hcj7-qf5w
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB