ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-106110

ImageSharp: TIFF CCITT T4 encoder can write past its compressed output buffer

Published Oct 7, 2026 · catalog updated Oct 26, 2026 · ImageSharp: TIFF CCITT T4

Last checked Oct 28, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-106110. EPSS is 0.39%. Act only if a listed version of ImageSharp: TIFF CCITT T4 is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (ImageSharp: TIFF CCITT T4).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.39%
Remediation
Advisory link
Affected products
NuGet SixLabors.ImageSharp

### Summary ImageSharp's TIFF CCITT Group 3 (T4) encoder can write beyond its allocated compressed-data buffer when encoding narrow 1-bit images. The unchecked writes can corrupt process memory and terminate the process. This report concerns only the T4 encoder path. It replaces the prior, unrelated ICC content. ### Affected package and versions - Package: (NuGet) - Affected range: - Commit corresponds to release **v4.1.1**. The T4 encoder and its undersized buffer calculation first shipped in v2.0.0. The narrow-image exploit terminates published v2.0.0 and v4.1.1 while the same-height 64-pixel control succeeds on both. Every release through v4.1.1 retains the vulnerable allocation and unchecked bit-write structure. ### Preconditions and impact The affected path is reached when the application encodes 1-bit image data with . This can happen when an application explicitly selects and . It can also occur when an application decodes a TIFF and re-encodes it using the default , because ImageSharp retains TIFF frame metadata including the compression and bit depth. creates for . allocates bytes, but non-modified T4 writes a 12-bit EOL before row data and an additional 12-bit EOL per row. calls and , both of which use without a capacity check. Thus the encoded bit stream can exceed the allocated span. A 1-pixel-wide, 2000-row alternating bilevel image caused a fatal during T4 compression. This is a memory-corruption and availability issue for applications that expose this encoding flow to attacker-controlled input. ### Tested environment - Package binary: NuGet **4.1.1** - Target framework: - Runtime: .NET 8.0.30; SDK 8.0.424 - Operating system: Debian GNU/Linux 12 (bookworm), Linux arm64, Docker No active exploitation is known. ### Reproduction In a project that references the published 4.1.1 binary, save the following as . Run for the trigger and for the control. Against the published 4.1.1 package, this produced: A 64-pixel-wide, 2000-row control using the same Group 3

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • NuGet SixLabors.ImageSharp2.0.0 → 3.2.0
  • NuGet SixLabors.ImageSharp4.0.0 → 4.1.2

How to fix CVE-2026-106110

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-106110. EPSS is 0.39%. Act only if a listed version of ImageSharp: TIFF CCITT T4 is installed.

Which versions are affected?

Compare what you have installed with SixLabors.ImageSharp 2.0.0 → 3.2.0; SixLabors.ImageSharp 4.0.0 → 4.1.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-787: Out-of-bounds Write. EPSS 0.39%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 7, 2026 · GitHub Advisory Database

    Detected

    ### Summary ImageSharp's TIFF CCITT Group 3 (T4) encoder can write beyond its allocated compressed-data buffer when encoding narrow 1-bit images. The unchecked writes can corrupt process memory and terminate the process. This report concerns only the T4 encoder path. It replaces the prior, unrelated ICC content. ### Affected package and versions - Package: (NuGet) - Affected range: - Commit corres

  2. Oct 26, 2026 · GitHub Advisory Database

    Fix available

    SixLabors.ImageSharp fixed in 3.2.0; SixLabors.ImageSharp fixed in 4.1.2

  3. Oct 26, 2026 · GitHub Advisory Database

    Fix available

    SixLabors.ImageSharp fixed in 3.2.0

  4. Oct 26, 2026 · GitHub Advisory Database

    Fix available

    SixLabors.ImageSharp fixed in 4.1.2

  5. Oct 26, 2026 · GitHub Advisory Database

    Updated

    ### Summary ImageSharp's TIFF CCITT Group 3 (T4) encoder can write beyond its allocated compressed-data buffer when encoding narrow 1-bit images. The unchecked writes can corrupt process memory and terminate the process. This report concerns only the T4 encoder path. It replaces the prior, unrelated ICC content. ### Affected package and versions - Package: (NuGet) - Affected range: - Commit corres

Sources

References

Freshness

Last verified in this catalog Oct 26, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseOct 28, 2026
  • OpenSSF OSV / OSV ScannerOct 28, 2026
  • CVE.orgOct 27, 2026