Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

ImageSharp: Tiled fax TIFF: tile buffer sized by TileWidth but fax decompressor writes scanlines of ImageWidth — heap OOB write

CVE-2026-106118GHSA-v76p-62qx-wwq2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (imagesharp 4.1.1, 3.2.0; sixlabors.imagesharp 4.1.1, 3.2.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • NuGet imagesharp

    Affected
    >= 3.0.0, < 3.2.0>= 4.0.0, < 4.1.1
    Fixed in
    3.2.0, 4.1.1

  • NuGet sixlabors.imagesharp

    Affected
    >= 3.0.0, < 3.2.0>= 4.0.0, < 4.1.1
    Fixed in
    3.2.0, 4.1.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-106118: 0.60% estimated exploitation activity in the next 30 days; percentile 48.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary When decoding a tiled TIFF with fax compression (T4/T6/MH), `DecodeTilesChunky` allocates each tile buffer from TileWidth (`ceil(TileWidth*bpp/8)*TileLength` bytes) but constructs the fax decompressor with frame.Width: `TiffDecompressorsFactory` ignores the `isTiled/tileWidth/tileHeight` parameters entirely. The T4/T6/MH decompressors treat the full image width as the scanline length and advance (and really write, via read-modify-write bit ops) `frame.Width` bits per row, with no bounds check against the tile buffer. The very first tile therefore writes linearly out of bounds — about `ImageWidth/8` bytes per row × TileLength rows into a `TileWidth`-sized buffer. With ImageWidth=4,000,000, TileWidth=16, TileLength=16 this writes ~2 MB past a 32-byte buffer and kills the process deterministically; a T6 all-white variant advances the bit offset by >512 MB silently, showing an alarm-free heap-corruption window for the same defect. A crafted file fully controls the OOB…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 5 · amended ·

    Amended from osv record GHSA-v76p-62qx-wwq2

  2. Revision 4 · amended ·

    Amended from ghsa record GHSA-v76p-62qx-wwq2

  3. Revision 3 · amended ·

    Amended from ghsa record GHSA-v76p-62qx-wwq2

  4. Revision 2 · amended ·

    Amended from ghsa record GHSA-v76p-62qx-wwq2

  5. Revision 1 · created ·

    Published from osv record GHSA-v76p-62qx-wwq2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-106118

Advisory: ImageSharp: Tiled fax TIFF: tile buffer sized by TileWidth but fax decompressor writes scanlines of ImageWidth — heap OOB write
IDs: CVE-2026-106118, GHSA-v76p-62qx-wwq2
Record: https://patchnext.com/advisories/cve-2026-106118 (revision 5, source checked 27 Oct 2026, 06:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: imagesharp 4.1.1, 3.2.0; sixlabors.imagesharp 4.1.1, 3.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet imagesharp: affected >= 3.0.0, < 3.2.0; >= 4.0.0, < 4.1.1; fixed in 3.2.0, 4.1.1
- NuGet sixlabors.imagesharp: affected >= 3.0.0, < 3.2.0; >= 4.0.0, < 4.1.1; fixed in 3.2.0, 4.1.1

## Suggested inspection (read-only)
- NuGet imagesharp: check the installed version with your package manager.
- NuGet sixlabors.imagesharp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on imagesharp, sixlabors.imagesharp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v76p-62qx-wwq2 (OSV record GHSA-v76p-62qx-wwq2 lists affected ranges: NuGet imagesharp >=3.0.0 <4.1.1 (fixed))
- Verified: https://github.com/advisories/GHSA-v76p-62qx-wwq2 (GitHub-reviewed advisory GHSA-v76p-62qx-wwq2 lists affected ranges: NuGet imagesharp >=3.0.0 =4.0.0 <4.1.1)
- Verified: https://github.com/advisories/GHSA-v76p-62qx-wwq2 (GitHub-reviewed advisory GHSA-v76p-62qx-wwq2 lists affected ranges: NuGet sixlabors.imagesharp >=3.0.0 =4.0.0 <4.1.1)
- Verified: https://osv.dev/vulnerability/GHSA-v76p-62qx-wwq2 (OSV record GHSA-v76p-62qx-wwq2 lists affected ranges: NuGet sixlabors.imagesharp >=3.0.0 =4.0.0 <4.1.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…