Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-106113 high CVSS 7.5

Out-of-Bounds Write in SixLabors.ImageSharp (CVE-2026-106113)

Summary

Out-of-bounds write in SixLabors.ImageSharp (CVE-2026-106113). Risk of unauthorized operations or information disclosure. Exploitable via SixLabors.ImageSharp. Mitigation: upgrade to 4.1.2 or later.

Original description

The description as published by the source.

Summary

SixLabors.ImageSharp can terminate a process when an application decodes
an attacker-supplied 32-bit floating-point TIFF as Image and applies
HistogramEqualization(). An IEEE positive-infinity TIFF sample reaches a non-finite or otherwise out-of-range
HalfVector4 component, depending on the release. The histogram equalization path derives a luminance-based
histogram index without validating that result, reaching an unsafe out-of-range
access.

This report covers HistogramEqualization only. It does not claim Adaptive
Histogram Equalization or AutoLevel behavior.

Affected package and versions

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

TIFF decoding first shipped in v2.0.0; v1.0.4 has no TIFF decoder. The unsafe luminance-derived histogram index is present from v2.0.0 through v4.1.1. The positive-infinity TIFF PoC terminates published 2.0.0, 3.1.12, 4.0.0, and 4.1.1 with AccessViolationException, while the finite 0.5 control completes on each tested release.

Details

ColorNumerics.GetBT709Luminance can produce a luminance that does not map to a valid histogram index. [GrayscaleLevelsRowOperation.Invoke](https://github.com/SixLabors/ImageSharp/blob/0815358f9202a78bc7f3b83e19…

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-106113 has been found in SixLabors.ImageSharp.
Attackers can target a specific entry point like SixLabors.ImageSharp over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/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-106113" on the vendor's site.

CVE-2026-106113 (SixLabors.ImageSharp) — CWE-787 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: SixLabors.ImageSharp / HalfVector4 / HistogramEqualization / AccessViolationException
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

Out-of-bounds write (CWE-787) exists in SixLabors.ImageSharp. Attackers reach the vulnerable code path via SixLabors.ImageSharp without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of SixLabors.ImageSharp. Attack surface: SixLabors.ImageSharp / HalfVector4 / HistogramEqualization / AccessViolationException.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 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