Use After Free in SixLabors.ImageSharp

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• sixlabors imagesharpbefore 2.1.7
• sixlabors imagesharp3.1.0 and later · before 3.1.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

• SixLabors ImageSharp

  • >= 3.0.0, < 3.1.3, < 2.1.7affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2026-106118ImageSharp: Tiled fax TIFF: tile buffer sized by TileWidth but fax decompressor writes scanlines of ImageWidth — heap OOB write
  30Monitor
• CVE-2026-106117ImageSharp: CCITT fax decompression (T4/Modified Huffman): unbounded WriteBits overflows strip buffer — heap OOB write in SixLabors.ImageSharp
  30Monitor
• CVE-2026-106115ImageSharp: TIFF CCITT T6 encoder writes beyond an undersized output buffer
  30Monitor
• CVE-2026-106113ImageSharp: HistogramEqualization uses an unvalidated luminance as an unchecked histogram index
  30Monitor
• CVE-2026-106112ImageSharp: ICC LUT16 output channel count can write beyond Vector4
  30Monitor
• CVE-2026-106110ImageSharp: TIFF CCITT T4 encoder can write past its compressed output buffer
  30Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1free(dev->buf);2/* ... another thread is still running ... */3process(dev->buf);

1lock(&dev->lock);2free(dev->buf);3dev->buf = NULL;4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.