# CVE-2026-107216: Excelize ANCHORARRAY: mutually-referencing array formulas recurse unboundedly via re-entrant CalcCellValue, causing a fatal stack overflow > An attacker can cause a fatal stack overflow in the Excelize Go library by providing mutually-referencing array formulas, crashing the application. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed - **Fix available:** Yes - **Published:** 7 Oct 2026 - **Updated:** 7 Oct 2026 - **Also known as:** GHSA-wp2g-vpjj-g53r, GO-2026-6688 ## What is CVE-2026-107216? CVE-2026-107216 is a high-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, with no action from the victim. ### Official description Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.8.1 to 2.11.0, ANCHORARRAY recursively calls the exported CalcCellValue function, creating a fresh calculation context at each cycle and bypassing in-flight and iteration controls. ANCHORARRAY calls CalcCellValue instead of cellResolver, so each recursive hop receives a new calcContext and loses cycle state. When mutually referencing dynamic-array formulas are evaluated directly or through formula-evaluating APIs, each recursion hop resets the cycle budget and prevents completion-based caches from breaking the cycle, allowing an attacker to cause a fatal Go stack overflow and abort the process. No fixed version is available as of this review. Weakness: CWE-674 (Uncontrolled Recursion) ## Which versions are affected by CVE-2026-107216? 3 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.8.1 | 2.11.1-0.20260911060113-ea12859e43c6 | | `github.com/xuri/excelize/v2` | Go | From 2.8.1 | 2.11.1-0.20260911060113-ea12859e43c6 | | `github.com/xuri/excelize/v2` | Go | From 2.8.1 | 2.11.1-0.20260911060113-ea12859e43c6 | Products: Excelize Excelize. ## How do I fix CVE-2026-107216? Upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260911060113-ea12859e43c6 or later. ## Is CVE-2026-107216 being exploited? There is no known exploitation of CVE-2026-107216 in the wild and no public exploit code. ## 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-107216 and fix it if it is affected. What it is: CVE-2026-107216 is a high-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, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-107216 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/xuri/excelize/v2 (Go): affected from 2.8.1; fixed in 2.11.1-0.20260911060113-ea12859e43c6 - github.com/xuri/excelize/v2 (Go): affected from 2.8.1; fixed in 2.11.1-0.20260911060113-ea12859e43c6 - github.com/xuri/excelize/v2 (Go): affected from 2.8.1; fixed in 2.11.1-0.20260911060113-ea12859e43c6 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-107216/ (Markdown: https://insights.sbomify.com/CVE-2026-107216/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107216 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107216 - OSV: https://osv.dev/vulnerability/CVE-2026-107216 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-107216/ Summaries are generated and may contain mistakes; the official description above is the record.