# github.com/xuri/excelize (Go) vulnerabilities

3 known vulnerabilities (2 high, 1 medium), with the versions each affects and the releases that fix them.

## At a glance

- Latest release: v1.4.0 (Sep 13, 2018): affected by 3 advisories
- Newest unaffected release: Every release is affected by at least one advisory
- Releases: 4 since v1.1.0 (Aug 19, 2017)
- Registry: https://pkg.go.dev/github.com/xuri/excelize
- Releases read: Nov 8, 2026

## Version timeline

Affected versions per advisory, in version order:

- CVE-2026-107217: v1.1.0 to v1.4.0 (through the newest release)
- CVE-2026-59162: v1.1.0 to v1.4.0 (through the newest release)
- CVE-2026-59161: v1.1.0 to v1.4.0 (through the newest release)

## Advisories (3)

### [CVE-2026-107217](https://cve.now/CVE-2026-107217): Excelize ColumnNameToNumber: int64 overflow yields an out-of-domain coordinate with nil error, causing negative slice index panic on r="0" rows

- Severity: High 7.5
- Published: Oct 7, 2026
- Affected: from 1.1.0, through 1.4.1.
- No fix released. The latest release, v1.4.0, is still affected.

### [CVE-2026-59162](https://cve.now/CVE-2026-59162): Excelize: Negative shared-string index causes panic in GetCellValue and GetRows

- Severity: Medium 6.9
- Published: Jul 10, 2026
- Affected: through 1.4.0.
- No fix released. The latest release, v1.4.0, is still affected.

### [CVE-2026-59161](https://cve.now/CVE-2026-59161): Excelize: Streaming GetRows row-bound bypass causes attacker-controlled allocation

- Severity: High 8.7
- Published: Jul 10, 2026
- Affected: through 1.4.0.
- No fix released. The latest release, v1.4.0, is still affected.

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/packages/go/github.com/xuri/excelize
Site guide for agents: https://cve.now/llms.txt
Uses NVD data; not endorsed by NVD.