Skip to main content
VulnerabilityPublished

CVE-2026-106113: SixLabors ImageSharp · Out-of-bounds Write

Affects SixLabors ImageSharpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 4.1.2 soon.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade ImageSharp and sixlabors.imagesharp to 4.1.2.

Affected software

ProductAffectedFixed in
SixLaborsImageSharpAffected
  • >=2.0.0 <4.1.2
Fixed in
  • 4.1.2
NuGetsixlabors.imagesharppkg:nuget/sixlabors.imagesharpOther threatsAffected
  • >=2.0.0 <4.1.2
Fixed in
  • 4.1.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, avoid processing untrusted 32-bit floating-point TIFF images with HistogramEqualization() in affected versions. No vendor advisory or patch links were provided in the input data.

Description

SixLabors.ImageSharp versions 2.0.0 through 4.1.1 contain an out-of-bounds write vulnerability triggered when decoding a specially crafted 32-bit floating-point TIFF image as Image<HalfVector4> and applying HistogramEqualization(). The issue arises from an unchecked luminance-derived histogram index that can be out-of-range due to positive-infinity TIFF samples, causing an AccessViolationException and process termination. No active exploitation is known.

References

Community reviews

Loading reviews…