Is github.com/xuri/excelize 1.3 vulnerable?
Go · 1 release from 1.3.0 to 1.3.0 · latest github.com/xuri/excelize is 1.4.1 · checked 18 Nov 2026
Yes: 4 known advisories
Yes. github.com/xuri/excelize 1.3.0, the last 1.3 release, is affected by 4 known security advisories (2 high, 1 medium, 1 low), including CVE-2026-107217, CVE-2026-59161, CVE-2026-59162. At least one has no fixed release yet.
Is your project on an affected github.com/xuri/excelize?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/xuri/excelize 1.3.0
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
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
Excelize: Streaming GetRows row-bound bypass causes attacker-controlled allocation
- Affected
- <=1.4.0
- Fixed in
- No fix released
Excelize: Negative shared-string index causes panic in GetCellValue and GetRows
- Affected
- <=1.4.0
- Fixed in
- No fix released
Which of your client projects are still on github.com/xuri/excelize 1.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/xuri/excelize version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/xuri/excelize versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.