Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-107213 medium CVSS 5.5

Vulnerability in github.com/xuri/excelize/v2 (CVE-2026-107213)

Summary

Vulnerability in github.com/xuri/excelize/v2 (CVE-2026-107213). Risk of unauthorized operations or information disclosure. Exploitable via ws.Drawing.RID. Mitigation: upgrade to 2.11.1-0.20260929015830-8ffeb07ec9a3 or later.

Original description

The description as published by the source.

Summary

GetSlicers guards only if ws.ExtLst == nil { return } (slicer.go:816-818) and then immediately dereferences ws.Drawing.RID with no nil check on ws.Drawing itself. Drawing and ExtLst are two independently optional child elements of in xl/worksheets/sheetN.xml, populated separately by encoding/xml depending on whether each tag is present. I executed a PoC: took a plain NewFile() workbook (no drawing, no slicer), saved it, then injected a bare immediately before in xl/worksheets/sheet1.xml (no other change, no drawing element present) and called GetSlicers. Result: runtime error: invalid memory address or nil pointer dereference, confirmed at the ws.Drawing.RID line via stack trace.

Reachability / who can trigger this

Unauthenticated: any application that opens an untrusted .xlsx and calls the public File.GetSlicers(sheet) API. The trigger is a single empty XML tag with no valid slicer or drawing content required at all, making it an even smaller/simpler payload than candidate 1.

Proof of Concept / Reproduction

Method:

  1. Reused the existing clone at C:\Users\vatsa\AppData\Local\Temp\claude\D--\59901fa2-b549-40e1-a433-30c8a3d01718\scratchpad\CVE-Hunt-10k\repos\qax-os__excelize (origin=https://github.com/qax-os/excelize.git, branch master up to date, commit e81f05008b33232151a58f06474fad5f70c4d060 dated 2026-09-27, git describe=v2.11.0-42-ge81f050, i.e. 42 commits past the v2.11.0 tag). 2) Manually re-read the cited source myself…

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-107213 has been found in github.com/xuri/excelize/v2.
Attackers can target a specific entry point like ws.Drawing.RID over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260929015830-8ffeb07ec9a3 or later.
If unsure, ask your IT team or search "github.com/xuri/excelize/v2 CVE-2026-107213" on the vendor's site.

CVE-2026-107213 (github.com/xuri/excelize/v2) — CWE-476 / CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: ws.Drawing.RID / Drawing / ExtLst
Patched: 2.11.1-0.20260929015830-8ffeb07ec9a3 — 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-476) exists in github.com/xuri/excelize/v2. Attackers reach the vulnerable code path via ws.Drawing.RID.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/xuri/excelize/v2. Attack surface: ws.Drawing.RID / Drawing / ExtLst.

🔥 Severity

Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.11.1-0.20260929015830-8ffeb07ec9a3.

🛡️ 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 'github.com/xuri/excelize/v2' . 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 'github.com/xuri/excelize/v2' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260929015830-8ffeb07ec9a3

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

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

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

Affected packages

go github.com/xuri/excelize/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.1-0.20260929015830-8ffeb07ec9a3"}]}]

References

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