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

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

Summary

Vulnerability in github.com/xuri/excelize/v2 (CVE-2026-107217). Risk of unauthorized operations or information disclosure. Exploitable via ColumnNameToNumber. Mitigation: upgrade to 2.11.1-0.20260910071107-696050fbf14e or later.

Original description

The description as published by the source.

Summary

ColumnNameToNumber (lib.go:220-237) accumulates the bijective base-26 value of a column name in an int64 with only an upper-bound check (col > MaxColumns) applied after the loop and no overflow detection. A 14-letter column name whose true value is 3·2⁶⁴ — e.g. VGWQHXLSDVIKWV — wraps to col = 0 and passes the guard, so CellNameToCoordinates("VGWQHXLSDVIKWV1") returns (col=0, row=1, err=nil).

When normalizing a r="0" row, checkSheetR0 (excelize.go:417-443, called from checkSheet at excelize.go:405) runs its checkRow closure with col = 0: colIdx := col - 1 becomes -1, and sheetData.Row[rowIdx].C[-1] (excelize.go:424) raises an unrecovered panic: runtime error: index out of range [-1], killing the host process.

Details

  • The row side of the same coordinate gate is enforced (checkRowNum at excelize.go:342-350 bounds r before the make([]xlsxRow, row) allocation; this includes the fix for GHSA-h69g-9hx6-f3v4 / CVE-2026-54063, present in the audited commit). The column side is not: checkSheet/lastRowNum/checkSheetR0 treat err == nil from CellNameToCoordinates as proof of an in-domain coordinate (excelize.go:356, :438), which is unsound because of the wrap-around above.
  • The same unsound gate also feeds ws.SheetData.Row[rowIdx].C[colNum-1] in xlsxWorksheet.checkRow (rows.go:969): a row combining a valid large column (e.g. XFD1) with an overflowed column panics identically.
  • Reachable from any `workShe…

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

CVE-2026-107217 (github.com/xuri/excelize/v2) — CWE-129 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ColumnNameToNumber / VGWQHXLSDVIKWV / checkSheetR0 / checkSheet
Patched: 2.11.1-0.20260910071107-696050fbf14e — 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-129) exists in github.com/xuri/excelize/v2. Attackers reach the vulnerable code path via ColumnNameToNumber without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/xuri/excelize/v2. Attack surface: ColumnNameToNumber / VGWQHXLSDVIKWV / checkSheetR0 / checkSheet.

🔥 Severity

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

🔧 How to fix

Update to 2.11.1-0.20260910071107-696050fbf14e.

🛡️ 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.20260910071107-696050fbf14e

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

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

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

Affected packages

go github.com/xuri/excelize/v2
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.11.1-0.20260910071107-696050fbf14e"}]}]
go github.com/xuri/excelize
[{"type":"SEMVER","events":[{"introduced":"1.1.0"},{"last_affected":"1.4.1"}]}]

References

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