Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

Excelize: Negative shared-string index causes panic in GetCellValue and GetRows

CVE-2026-59162GHSA-fx5j-qcqg-grpf

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/xuri/excelize

    Affected
    <= 1.4.0
    Fixed in
    no fixed version recorded

  • Go github.com/xuri/excelize/v2

    Affected
    < 2.11.0
    Fixed in
    2.11.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-59162: 0.66% estimated exploitation activity in the next 30 days; percentile 51.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Negative shared-string index causes panic in GetCellValue and GetRows Summary Excelize parses shared-string cell values with strconv.Atoi and checks only the upper bound before indexing the shared string slice. If an XLSX file contains a shared-string cell with <v-1</v, the parsed index is negative. The upper-bound check still passes (len(sharedStrings) -1), and Excelize indexes sharedStrings[-1], causing a runtime panic. This was reproduced on the current default branch commit 1213a8bd7c5ab360554603ac5c995ccaf6eb4314 and the latest release tag v2.10.1 (5ad5ab3af0054c55bdce09f1530085600e9f2e45). The issue is independent from the row-bound allocation report, so I am reporting it separately. Affected package - Package: github.com/xuri/excelize/v2 - Tested affected versions: current default branch at 1213a8bd7c5ab360554603ac5c995ccaf6eb4314, and release v2.10.1 - Fixed version: none known at the time of this report Impact An attacker who can provide an XLSX file to an application using…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-fx5j-qcqg-grpf

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6452

  4. Revision 1 · created ·

    Published from osv record GHSA-fx5j-qcqg-grpf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-59162

Advisory: Excelize: Negative shared-string index causes panic in GetCellValue and GetRows
IDs: CVE-2026-59162, GHSA-fx5j-qcqg-grpf
Record: https://patchnext.com/advisories/cve-2026-59162 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/xuri/excelize/v2 2.11.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/xuri/excelize: affected <= 1.4.0
- Go github.com/xuri/excelize/v2: affected < 2.11.0; fixed in 2.11.0

## Suggested inspection (read-only)
- Go github.com/xuri/excelize: check the installed version with your package manager.
- Go github.com/xuri/excelize/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/xuri/excelize, github.com/xuri/excelize/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-fx5j-qcqg-grpf (OSV record GHSA-fx5j-qcqg-grpf lists affected ranges: Go github.com/xuri/excelize/v2 >=0 =0 <=1.4.0)
- Verified: https://osv.dev/vulnerability/GO-2026-6452 (OSV record GO-2026-6452 lists affected ranges: Go github.com/xuri/excelize/v2 >=0 <2.11.0 (fixed))
- Verified: https://github.com/advisories/GHSA-fx5j-qcqg-grpf (GitHub-reviewed advisory GHSA-fx5j-qcqg-grpf lists affected ranges: Go github.com/xuri/excelize/v2 >=0 =0 <=1.4.0)

Commands are suggestions: review each one before running it.

Loading voting…