Quick answers
- Is CVE-2026-106111 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106111 being exploited in the wild.
- How severe is CVE-2026-106111?
- Medium severity, with a CVSS score of 5.9, published 6 October 2026.
- Which products and versions are affected?
- SixLabors.ImageSharp (NuGet) >= 4.0.0, <= 4.1.1, ECOSYSTEM:introduced=4.0.0,fixed=4.1.2; SixLabors ImageSharp 4.0.0 through 4.1.1.
- Is there a fix for CVE-2026-106111?
- 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-106111 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106111?
- 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 ExrBaseDecompressor.UndoZipCompression method accepts ZIP decompression output shorter than expected without validation. When ZipExrCompression.Decompress reconstructs a partial buffer and ExrDecoderCore processes the full expected block using uninitialized or leftover memory from Configuration.Default, process-local image data becomes accessible in the decoded pixels. This affects EXR files with ZIP or ZIPS compression from versions 4.0.0 through 4.1.1; the vulnerability requires the attacker to control the EXR file being decoded.
Affected products
- SixLabors ImageSharp 4.0.0 through 4.1.1
Identifiers
- CVE-2026-106111
- GHSA-4q3p-rj5x-xv7p
Timeline
- 2026-10-06: disclosed