# CVE-2026-107225: Excelize: GetStyle panics on a negative fillId, borderId or fontId in styles.xml

> An attacker can cause a denial of service by providing a crafted Excel file with negative style indices, triggering a panic in the Excelize library.

- **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:** 10 Oct 2026
- **Also known as:** GHSA-5h23-36rv-pm65

## What is CVE-2026-107225?

CVE-2026-107225 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.8.0 to 2.11.0, GetStyle's fill, border, and font extraction predicates check only upper bounds for attacker-controlled style-table indices. File.GetStyle relies on extractStyleCondFuncs predicates that allow negative FillID, BorderID, and FontID values to reach slice indexing. When a crafted styles.xml supplies a negative fillId, borderId, or fontId and the application reads the style, a negative identifier passes the upper-bound-only predicate and becomes a negative slice index, allowing an attacker to panic while reading cell styling. No fixed version is available as of this review.

Weakness: CWE-20 (Improper Input Validation), CWE-129 (Improper Validation of Array Index)

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

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.8.0 | 2.11.1-0.20260731010303-ae2113b410e5 |
| `github.com/xuri/excelize/v2` | Go | From 2.8.0 | 2.11.1-0.20260731010303-ae2113b410e5 |

Products: Excelize Excelize.

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

Upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260731010303-ae2113b410e5 or later.

## Is CVE-2026-107225 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107225 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-107225 and fix it if it is affected.

What it is: CVE-2026-107225 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-107225 exists.

Affected packages and fixed versions:
- github.com/xuri/excelize/v2 (Go): affected from 2.8.0; fixed in 2.11.1-0.20260731010303-ae2113b410e5
- github.com/xuri/excelize/v2 (Go): affected from 2.8.0; fixed in 2.11.1-0.20260731010303-ae2113b410e5

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

## Sources

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

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