github.com/360EntSecGroup-Skylar/excelize/v2 vulnerabilities

Registry
Go
Latest
2.11.1

6 known advisories

The latest version, 2.11.1, is affected by 6 of them.

Is your project on an affected github.com/360EntSecGroup-Skylar/excelize/v2?

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/360EntSecGroup-Skylar/excelize/v2

  • LowCVE-2026-107223GO-2026-66785 Nov 2026

    Unbounded <col max> lacks MaxColumns check in flatCols(), causing column mutators to hang or OOM in github.com/xuri/excelize

    Affected
    >=2.1.0
    Fixed in
    No fix released
  • LowCVE-2026-107224GO-2026-66795 Nov 2026

    Excelize: A Zip64 uncompressed-size of 2^63 panics OpenFile/OpenReader in github.com/xuri/excelize

    Affected
    >=2.1.0
    Fixed in
    No fix released
  • LowCVE-2026-107219GO-2026-66815 Nov 2026

    Excelize: Unbounded spinCount in agile decryption burns CPU during OpenFile in github.com/xuri/excelize

    Affected
    >=2.3.1
    Fixed in
    No fix released
  • LowCVE-2026-107214GO-2026-668419 Oct 2026

    Excelize Decrypt: unrecoverable panics on malformed OLE/CFB encrypted workbooks in github.com/xuri/excelize

    Affected
    >=2.3.1
    Fixed in
    No fix released
  • LowCVE-2026-107212GO-2026-668519 Oct 2026

    Excelize: Unbounded row number in Rows.Columns makes GetRows and the Rows iterator loop for days in github.com/xuri/excelize

    Affected
    >=2.1.0
    Fixed in
    No fix released
  • LowCVE-2026-107215GO-2026-668919 Oct 2026

    Panic and memory exhaustion via unbounded CFB stream allocation in github.com/xuri/excelize

    Affected
    >=2.3.1
    Fixed in
    No fix released

Is your github.com/360EntSecGroup-Skylar/excelize/v2 version vulnerable?

Which of your client projects still run an old github.com/360EntSecGroup-Skylar/excelize/v2?

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.