# CVE-2026-107219: Excelize: Unbounded spinCount in agile decryption burns CPU during OpenFile

> An attacker can cause CPU exhaustion in applications using Excelize by providing a crafted Excel file with an excessive spinCount during decryption.

- **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-jrfj-fhj2-jjvm

## What is CVE-2026-107219?

CVE-2026-107219 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.3.1 to 2.11.0, agile decryption accepts an attacker-controlled spinCount and performs that many password-key derivation iterations before verifier validation. OpenFile reaches agileDecrypt, which passes the unbounded spinCount to convertPasswdToKey before password verification. When a crafted OLE encrypted-workbook header supplies an excessive spinCount and the file is opened, the key-derivation loop performs unbounded attacker-selected work and cannot be cancelled, allowing an attacker to consume a CPU core for an attacker-controlled duration. No fixed version is available as of this review.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-107219?

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.3.1 | 2.11.1-0.20260906004932-2badfcd5841d |
| `github.com/xuri/excelize/v2` | Go | From 2.3.1 | 2.11.1-0.20260906004932-2badfcd5841d |

Products: Excelize Excelize.

## How do I fix CVE-2026-107219?

Upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260906004932-2badfcd5841d or later.

## Is CVE-2026-107219 being exploited?

There is no known exploitation of CVE-2026-107219 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-107219 and fix it if it is affected.

What it is: CVE-2026-107219 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-107219 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/xuri/excelize/v2 (Go): affected from 2.3.1; fixed in 2.11.1-0.20260906004932-2badfcd5841d
- github.com/xuri/excelize/v2 (Go): affected from 2.3.1; fixed in 2.11.1-0.20260906004932-2badfcd5841d

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-107219/ (Markdown: https://insights.sbomify.com/CVE-2026-107219/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107219
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107219
- OSV: https://osv.dev/vulnerability/CVE-2026-107219

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107219/
Summaries are generated and may contain mistakes; the official description above is the record.