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

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

Summary

Vulnerability in github.com/xuri/excelize/v2 (CVE-2026-107214). Risk of unauthorized operations or information disclosure. Exploitable via OpenFile. Mitigation: upgrade to 2.11.1-0.20260915055537-22f76f9acb94 or later.

Original description

The description as published by the source.

Summary

Any file whose first 8 bytes are the OLE compound-file signature (D0 CF 11 E0 A1 B1 1A E1) is routed by OpenFile/OpenReader/OpenBytes → openReaderAt → Decrypt. The version dispatch only guarantees len(EncryptionInfo) >= 4 before handing attacker-controlled EncryptionInfo/EncryptedPackage buffers to standardDecrypt/agileDecrypt, and no callee validates structure. Malformed but version-valid content therefore fails as an unrecovered runtime panic instead of an error, terminating the calling process.

Details

All panic classes below were execution-confirmed against pristine master (ecd99d761fe0, 2026-09-08). excelize.go:211-213 maps Decrypt errors to ErrWorkbookFileFormat, but panics bypass that path and kill the process.

# Malformed input Panic Site
1 standard, len(EncryptionInfo) 4–11 slice bounds [:12] crypt.go:238
2 standard, attacker-controlled headerSize uint32 slice bounds [12:12+headerSize] / fixed-offset header reads crypt.go:238-249
3 standard, verifier remainder < 72 (AES) / 60 (RC4) bytes slice bounds in standardEncryptionVerifier crypt.go:282-295
4 standard, header.KeySize = 0xFFFFFFFF slice bounds [:536870911] with capacity 48 crypt.go:321
5 standard, EncryptedPackage stream missing/short slice bounds [8:0] crypt.go:268
6 agile, len(EncryptionInfo) 4–7 slice bounds [8:4] crypt.go:407
7 a…

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-107214 has been found in github.com/xuri/excelize/v2.
Attackers can target a specific entry point like OpenFile 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.20260915055537-22f76f9acb94 or later.
If unsure, ask your IT team or search "github.com/xuri/excelize/v2 CVE-2026-107214" on the vendor's site.

CVE-2026-107214 (github.com/xuri/excelize/v2) — CWE-248 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: OpenFile / OpenReader / OpenBytes / openReaderAt
Patched: 2.11.1-0.20260915055537-22f76f9acb94 — 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-248) exists in github.com/xuri/excelize/v2. Attackers reach the vulnerable code path via OpenFile without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/xuri/excelize/v2. Attack surface: OpenFile / OpenReader / OpenBytes / openReaderAt.

🔥 Severity

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

🔧 How to fix

Update to 2.11.1-0.20260915055537-22f76f9acb94.

🛡️ 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.20260915055537-22f76f9acb94

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

  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.20260915055537-22f76f9acb94"}]}]

References

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