Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-106111 medium CVSS 5.9

Vulnerability in SixLabors.ImageSharp (CVE-2026-106111)

Summary

Vulnerability in SixLabors.ImageSharp (CVE-2026-106111). Confidential information can be exposed externally. Exploitable via Configuration.Default. Mitigation: upgrade to 4.1.2 or later.

Original description

The description as published by the source.

Summary

A crafted ZIP-compressed OpenEXR image can return stale memory from a prior
ImageSharp operation as decoded pixels. The ZIP decoder accepts a non-empty
inflate result shorter than the EXR block's required size, then the EXR decoder
reads the full expected block.

This is a process-local, cross-operation information-disclosure defect. It is
relevant when an application uses the shared Configuration.Default allocator
for separate image operations and exposes pixels or output derived from a later
attacker-controlled EXR decode. Whether that creates a network attack path
depends on the host application.

No active exploitation is known.

Affected package and versions

  • Package: SixLabors.ImageSharp (NuGet)
  • Affected published releases: 4.0.0, 4.1.0, and 4.1.1
  • Affected range: >= 4.0.0, <= 4.1.1
  • Commit 0815358f9202a78bc7f3b83e19282dc3654b500f corresponds to release v4.1.1.

EXR support first appears in v4.0.0. The cross-operation PoC exposes the prior-operation marker on each published 4.x release, while the full-inflate control does not expose it on any of them.

Details

For ZIP/ZIPS EXR compression, ExrDecoderCore
allocates the expected block buffer without AllocationOptions.Clean and later
interprets the complete buffer as channel data. [ZipExrCompression](https://github.com/SixLabors/ImageSh…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-106111 has been found in SixLabors.ImageSharp.
Attackers can target a specific entry point like Configuration.Default over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade SixLabors.ImageSharp to 4.1.2 or later.
If unsure, ask your IT team or search "SixLabors.ImageSharp CVE-2026-106111" on the vendor's site.

CVE-2026-106111 (SixLabors.ImageSharp) — CWE-226 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Configuration.Default / SixLabors.ImageSharp / ExrDecoderCore / AllocationOptions.Clean
Patched: 4.1.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-226) exists in SixLabors.ImageSharp. Attackers reach the vulnerable code path via Configuration.Default without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of SixLabors.ImageSharp. Attack surface: Configuration.Default / SixLabors.ImageSharp / ExrDecoderCore / AllocationOptions.Clean.

🔥 Severity

Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.1.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'SixLabors.ImageSharp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'SixLabors.ImageSharp' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で SixLabors.ImageSharp を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade SixLabors.ImageSharp to 4.1.2

    ステージング環境で 4.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

nuget SixLabors.ImageSharp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details