Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessUpload crafted narrow 1-bit TIFF
-
DeliveryTrigger CCITT Group 3 re-encode path
-
ExploitUnder-allocated buffer overflowed in CompressStrip
-
ExecutionProcess memory corrupted and crash
-
ImpactDenial 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 that CCITT Group 3 fax compression (TiffCompression.CcittGroup3Fax) is used during TIFF encoding - either selected explicitly by the host application or inherited automatically from a decoded TIFF's metadata in a decode-and-re-encode flow - AND that the image being encoded is a narrow 1-bit image that triggers the undersized buffer allocation in TiffCcittCompressor.Initialize. Limiting factors that reduce real-world risk: the flaw is in the TIFF *encode* path, so an application that only decodes images is not affected unless it re-encodes; applications that never select CCITT Group 3 compression and never process attacker-supplied TIFF metadata that sets it are not reachable; and the impact is limited to process termination (DoS), not confidentiality or integrity loss. Affected versions are ImageSharp 2.0.0 through 4.1.1. |
| Impact | This is a classic high-CVSS-but-bounded-impact availability flaw rather than a top-tier emergency. The NVD vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H = 7.5) scores entirely on availability: the CWE-787 out-of-bounds write corrupts process memory and terminates the process (denial of service), with no confidentiality or integrity impact and no indication of code execution despite the 'corrupt process memory' wording. No EPSS score, KEV listing, POC, or SSVC decision data was provided, so there is no public exploit identified at time of analysis and no evidence of active or automatable exploitation - the 7.5 reflects theoretical remote reachability, not demonstrated weaponization. A key conflict to verify: the AV:N/PR:N/AC:L vector implies trivial remote unauthenticated abuse, but the description's exploitation path is conditional - it fires only when TiffCompression.CcittGroup3Fax is selected (either explicitly by the application or inherited from decoded TIFF metadata) and only for narrow 1-bit images, which narrows real-world exposure well below what the raw score suggests. Priority should be moderate: patch promptly where ImageSharp handles untrusted TIFFs in a decode-and-re-encode pipeline, but it is not a drop-everything issue absent exploitation signals. |
| Exploit ScenarioDerived | An application uses ImageSharp (2.0.0-4.1.1) to accept user-uploaded TIFF images and re-encode them, with CCITT Group 3 fax compression either configured or inherited from the uploaded file's metadata. An attacker submits a crafted narrow 1-bit TIFF so that TiffCcittCompressor.Initialize under-allocates the compressed-data buffer and T4BitCompressor.CompressStrip writes past the output span, corrupting memory and crashing the worker process to cause denial of service. No public proof-of-concept was provided in the intelligence sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
TIFF encoding in SixLabors ImageSharp 2.0.0 through 4.1.1 can write past the end of an undersized compressed-data buffer when CCITT Group 3 fax compression is used on narrow 1-bit images, corrupting process memory and typically terminating the process. The flaw is reachable by remote, unauthenticated attackers (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) only when the host application either explicitly selects TiffCompression.CcittGroup3Fax during encoding or inherits that compression setting from attacker-supplied TIFF metadata in a decode-and-re-encode flow; the impact is limited to availability (denial of service), with no confidentiality or integrity loss assessed. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has released a fixed version, 4.1.2.
RemediationAI
Vendor-released patch: upgrade SixLabors.ImageSharp to version 4.1.2 or later, which is the fix identified in the advisory https://github.com/SixLabors/ImageSharp/security/advisories/GHSA-j9gm-c75j-xc9q and the release https://github.com/SixLabors/ImageSharp/releases/tag/v4.1.2; the corrective change is in pull request https://github.com/SixLabors/ImageSharp/pull/3187 (commit a9498c6db3642ef92c712ebc81e706914ac16a95). If immediate upgrade is not possible, apply compensating controls that break the required preconditions: (1) avoid using TiffCompression.CcittGroup3Fax for TIFF encoding and switch to a different compression mode or a different output format - this fully removes reachability but changes output file characteristics and size; (2) for services that accept untrusted TIFFs, strip or explicitly override TIFF compression metadata before any re-encode step so an attacker cannot force CCITT Group 3 selection through a decoded file's inherited metadata - this requires pipeline changes and careful testing to avoid altering legitimate output; (3) isolate TIFF encode/re-encode processing in a separate, resource-limited worker process or sandbox with restart-on-failure so that memory corruption results in a contained worker crash rather than loss of the primary service - this is a containment measure that does not fix the bug and adds operational overhead. Note that this is a denial-of-service (availability-only) issue in the encode path; no confidentiality or integrity impact has been assessed.
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
The root cause class is CWE-787, out-of-bounds write. ImageSharp implements TIFF CCITT Group 3 (T.4) fax compression through TiffCcittCompressor and T4BitCompressor; TiffCcittCompressor.Initialize computes the size of the compressed-data buffer but under-reserves for narrow 1-bit images, failing to account for the full row data plus the T4 end-of-line codes that the encoder emits. When T4BitCompressor.CompressStrip then writes the encoded strip, those unchecked writes extend beyond the logical output span and corrupt adjacent memory. Triggering the path requires TiffCompression.CcittGroup3Fax to be active for the encode operation - either chosen directly by the caller or propagated from the metadata of a decoded TIFF during a decode-and-re-encode workflow - combined with an image geometry narrow enough to expose the allocation shortfall. The CPE entry (cpe:2.3:a:sixlabors:imagesharp:*:*:*:*:*:*:*:*) confirms the affected component is the SixLabors ImageSharp library broadly across versions in the range. The vendor fix landed alongside broader input-validation hardening in the same pull request and release, including stricter bounds checks in ICC colour-profile calculators (CLUT/LUT/TRC channel counts) and new stream range-validation helpers (BufferedReadStreamExtensions.IsReadRangeValid / TryGetReadLength), which reflect the same defensive theme of validating untrusted lengths and offsets before reading or writing.
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
Attacker-supplied TIFF metadata can inherit the vulnerable CCITT compression over a re-encode pipeline (AV:N/PR:N/UI:N); crafted input is deterministic (AC:L); impact is process crash only, so C:N/I:N/A:H.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
ImageSharp is a 2D graphics library. From 2.0.0 until 4.1.2, the TIFF CCITT Group 3 encoder allocates an undersized compressed-data buffer for narrow 1-bit images. TiffCcittCompressor.Initialize does not reserve enough space for the row data and T4 end-of-line codes, and T4BitCompressor.CompressStrip reaches unchecked writes when TiffCompression.CcittGroup3Fax is selected directly or inherited from decoded TIFF metadata. An attacker-controlled encode or decode-and-re-encode flow can write beyond the logical output span, corrupt process 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 3 / T4 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
A memory-corruption flaw in SixLabors ImageSharp, a widely used .NET image-processing library, lets a remote, unauthenticated party crash the application process simply by supplying a crafted TIFF file on affected versions 2.0.0 through 4.1.1. Because ImageSharp is typically embedded in web services, document pipelines, and upload-handling endpoints, the practical effect is unplanned outages of customer-facing or revenue-supporting services rather than theft or alteration of data. Leadership should care because the fix is a low-effort library upgrade, while the exposure is repeated denial-of-service against any internet-facing system that processes untrusted images.
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
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
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-93574
GHSA-j9gm-c75j-xc9q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB