github.com/xuri/excelize vulnerabilities

Registry
Go
Latest
1.4.1

4 known advisories

The latest version, 1.4.1, is affected by 2 of them.

Is your project on an affected github.com/xuri/excelize?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for github.com/xuri/excelize

  • LowCVE-2026-107217GO-2026-66775 Nov 2026

    Integer overflow yields an out-of-domain coordinate with nil error, causing panic in github.com/xuri/excelize

    Affected
    >=1.1.0
    Fixed in
    No fix released
  • HighCVE-2026-107217GHSA-c85p-xxjj-2r757 Oct 2026

    Excelize ColumnNameToNumber: int64 overflow yields an out-of-domain coordinate with nil error, causing negative slice index panic on r="0" rows

    Affected
    >=1.1.0 <=1.4.1
    Fixed in
    No fix released
  • HighCVE-2026-59161GHSA-q5j5-6p94-4gwc10 Sept 2026

    Excelize: Streaming GetRows row-bound bypass causes attacker-controlled allocation

    Affected
    <=1.4.0
    Fixed in
    No fix released
  • MediumCVE-2026-59162GHSA-fx5j-qcqg-grpf10 Sept 2026

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

    Affected
    <=1.4.0
    Fixed in
    No fix released

Is your github.com/xuri/excelize version vulnerable?

Which of your client projects still run an old github.com/xuri/excelize?

NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Go packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.