CVE-2026-107216 json
Excelize ANCHORARRAY: mutually-referencing array formulas recurse unboundedly via re-entrant CalcCellValue, causing a fatal stack overflow
published last mo. modified 21d ago also EUVD-2026-94534 , GHSA-wp2g-vpjj-g53r , GO-2026-6688
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/xuri/excelize/v2 2.11.1-0.20260911060113-ea12859e43c6
Is CVE-2026-107216 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/qax-os/excelize/security/advisories/GHSA-wp2g-vpjj-g53r referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/xuri/excelize/v2 | >=2.8.1, <2.11.1-0.20260911060113-ea12859e43c6 |
2.11.1-0.20260911060113-ea12859e43c6 |
Affected products
- qax-os excelize
Classification
- Weakness
-
- CWE-674 Uncontrolled Recursion
References
-
github.com
/qax-os/excelize/commit/ea12859e43c64d498ecf839263c5f917391f3316
web, patch
-
github.com
/qax-os/excelize/security/advisories/GHSA-wp2g-vpjj-g53r
web, exploit, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-107216
advisory
-
github.com
/qax-os/excelize
package
Sources
- CVE List CVE-2026-107216
- GitHub Advisory GHSA-wp2g-vpjj-g53r
- NVD CVE-2026-107216
- OSV GO-2026-6688
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.