# CVE-2026-107221: Excelize: a row whose earlier cell has a higher column reference than its last cell panics index out of range on almost every worksheet read API > A crafted Excel file causes a panic in the Excelize Go library, terminating the application during worksheet reading. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 7 Oct 2026 - **Updated:** 7 Oct 2026 - **Also known as:** GHSA-8mcq-6wmr-jrjv ## What is CVE-2026-107221? CVE-2026-107221 is a medium-severity denial of service vulnerability in qax-os excelize, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.0.0 to 2.11.0, checkRow sizes its target cell slice from the last cell in XML document order and then re-scatters every cell by its explicit column reference. GetCellValue reaches workSheetReader and checkRow, where targetList is too short for an earlier out-of-order cell. When a crafted row places a higher-column cell before a lower-column final cell and a non-streaming worksheet API reads the sheet, the earlier cell's column index exceeds the slice length derived from the final cell, allowing an attacker to cause an unrecovered panic and terminate the process. No fixed version is available as of this review. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2026-107221? 2 open source packages ship an affected version, including github.com/xuri/excelize/v2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/xuri/excelize/v2` | Go | From 2.0.0 | 2.11.1-0.20260816084418-46a5eb289448 | | `github.com/xuri/excelize/v2` | Go | From 2.0.0 | 2.11.1-0.20260816084418-46a5eb289448 | Products: Excelize Excelize. ## How do I fix CVE-2026-107221? Upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260816084418-46a5eb289448 or later. ## Is CVE-2026-107221 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107221 exists. ## Other vulnerabilities in qax-os excelize - [CVE-2026-107211](https://insights.sbomify.com/CVE-2026-107211/): Excelize: Unchecked pivot-cache field index in extractPivotTableFields causes unrecoverable panic (high 8.7) - [CVE-2026-107213](https://insights.sbomify.com/CVE-2026-107213/): Excelize: Nil-pointer dereference in GetSlicers when a worksheet has extLst present but no drawing element (high 8.7) - [CVE-2026-59161](https://insights.sbomify.com/CVE-2026-59161/): Excelize: Streaming GetRows row-bound bypass causes attacker-controlled allocation (high 8.7) - [CVE-2026-107212](https://insights.sbomify.com/CVE-2026-107212/): Excelize: Unbounded row number in Rows.Columns makes GetRows and the Rows iterator loop for days (high 7.5) - [CVE-2026-107214](https://insights.sbomify.com/CVE-2026-107214/): Excelize Decrypt: unrecoverable panics on malformed OLE/CFB encrypted workbooks (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-107221 and fix it if it is affected. What it is: CVE-2026-107221 is a medium-severity denial of service vulnerability in qax-os excelize, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107221 exists. Affected packages and fixed versions: - github.com/xuri/excelize/v2 (Go): affected from 2.0.0; fixed in 2.11.1-0.20260816084418-46a5eb289448 - github.com/xuri/excelize/v2 (Go): affected from 2.0.0; fixed in 2.11.1-0.20260816084418-46a5eb289448 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-107221/ (Markdown: https://insights.sbomify.com/CVE-2026-107221/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107221 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107221 - OSV: https://osv.dev/vulnerability/CVE-2026-107221 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-107221/ Summaries are generated and may contain mistakes; the official description above is the record.