Quick answers
- Is CVE-2026-106116 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106116 being exploited in the wild.
- How severe is CVE-2026-106116?
- Medium severity, with a CVSS score of 5.3, published 6 October 2026.
- Which products and versions are affected?
- SixLabors.ImageSharp (NuGet) >= 2.0.0, <= 4.1.1, ECOSYSTEM:introduced=2.0.0,fixed=4.1.2; SixLabors ImageSharp 2.0.0 to 4.1.1.
- Is there a fix for CVE-2026-106116?
- Yes. SixLabors.ImageSharp (NuGet): upgrade to 4.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106116 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106116?
- Check whether you run SixLabors.ImageSharp (NuGet) or SixLabors ImageSharp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- SixLabors.ImageSharp (NuGet): upgrade to 4.1.2 or later
dotnet add package SixLabors.ImageSharp --version 4.1.2
Technical details
The ExifReader.ReadValues64 method trusts the declared entry count in a BigTIFF IFD (Image File Directory) without validation and iterates once per entry. When fewer than 20 bytes remain in the stream, ReadValue64 returns without advancing the stream position or breaking the outer loop, causing an infinite loop. A network attacker can send a crafted BigTIFF image to trigger this condition, locking a single decoder thread indefinitely.
Affected products
- SixLabors ImageSharp 2.0.0 to 4.1.1
Identifiers
- CVE-2026-106116
- GHSA-wmxv-xphr-5c9g
Timeline
- 2026-10-06: disclosed
- 2026-09-12: patched