# Excelize ANCHORARRAY: mutually-referencing array formulas recurse unboundedly via re-entrant CalcCellValue, causing a fatal stack overflow

Advisory record · `GHSA-wp2g-vpjj-g53r`

- **Identifiers:** `GHSA-wp2g-vpjj-g53r` · `CVE-2026-107216` · `GO-2026-6688`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-674](https://cwe.mitre.org/data/definitions/674.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 8 Oct 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Oct 2026, 16:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/xuri/excelize/v2` (Go): affected `>=2.8.1, <2.11.1-0.20260911060113-ea12859e43c6`; fixed in `2.11.1-0.20260911060113-ea12859e43c6`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Excelize (github.com/xuri/excelize/v2) versions 2.8.1 up to but not including 2.11.1-0.20260911060113-ea12859e43c6 are vulnerable. A crafted workbook with two mutually referencing ANCHORARRAY dynamic array formulas causes unbounded recursion during formula evaluation, which ends in a fatal Go stack overflow that aborts the whole process. An attacker only needs to supply such a workbook to an application that evaluates its cells, such as through CalcCellValue, AddPivotTable, or AddPicture. Upgrade to 2.11.1-0.20260911060113-ea12859e43c6 or later. No configuration workaround is listed.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0037, the 31st percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wp2g-vpjj-g53r)

## Sources

- [GitHub Advisory Database: GHSA-wp2g-vpjj-g53r](https://github.com/advisories/GHSA-wp2g-vpjj-g53r)
- [OSV: GHSA-wp2g-vpjj-g53r](https://osv.dev/vulnerability/GHSA-wp2g-vpjj-g53r)
- <https://github.com/qax-os/excelize/security/advisories/GHSA-wp2g-vpjj-g53r>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-107216>
- <https://github.com/qax-os/excelize/commit/ea12859e43c64d498ecf839263c5f917391f3316>
- <https://github.com/qax-os/excelize>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wp2g-vpjj-g53r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wp2g-vpjj-g53r/>. Everything for agents: <https://agentprime.io/llms.txt>.