dbcve.org
ExcelizeApplication

CVE-2026-54063

HIGH · 7.5 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 2.11.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. Prior to 2.11.0, the checkSheet() function in github.com/xuri/excelize/v2 uses an attacker-controlled <row r="N"> XML attribute value directly as the length argument to make([]xlsxRow, row) without validating it against the Excel row limit (TotalRows = 1,048,576). A specially crafted XLSX file can trigger two denial-of-service variants: (A) an out-of-memory process kill when r=2147483647 forces a ~16 GB allocation attempt, and (B) a runtime panic via out-of-bounds slice indexing when r=-1. Any service that opens attacker-supplied XLSX files and calls GetCellValue is affected. No authentication is required. This issue is fixed in version 2.11.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Excelize Go library's checkSheet() function uses the XML row attribute value directly as a length argument to make() without validating against the Excel row limit (1,048,576). Attackers can craft XLSX files with r=2147483647 to trigger ~16GB allocation (OOM) or r=-1 to cause out-of-bounds slice indexing (panic). The vulnerability is triggered when GetCellValue is called on malicious files.

MitigationUpgrade Excelize to version 2.11.0 or later, which includes proper bounds validation on the row attribute. Until upgraded, do not open untrusted XLSX files with GetCellValue.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ExcelizeApplication
Affected:< 2.11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Excelize library usage
    Search your codebase for 'excelize' import statements or run 'go list -m all | grep excelize' to list the dependency
    Affected if The excelize library is present in your Go dependencies
  2. Check Excelize version
    Run 'go list -m -versions github.com/xuri/excelize' or inspect the version line in your go.mod file
    Affected if The installed version is lower than 2.11.0
  3. Identify GetCellValue usage
    Search your codebase for GetCellValue function calls that process XLSX files, such as 'excelize.GetCellValue'
    Affected if GetCellValue is used to read cell values from XLSX files in your application
  4. Assess file source trust
    Review code paths where GetCellValue is called to determine if they handle files from untrusted sources like user uploads, web requests, or external APIs
    Affected if GetCellValue processes files from untrusted or external sources

You are affected if you use Excelize version below 2.11.0 and your application calls GetCellValue on XLSX files from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.11.0 or later
Fixed in 2.11.0
Interim mitigation

Upgrade Excelize to version 2.11.0 or later, which includes proper bounds validation on the row attribute. Until upgraded, do not open untrusted XLSX files with GetCellValue.

Recommended fix High confidence

v2.11.0

  1. 1. Identify the current version of github.com/xuri/excelize/v2 in use by checking go.mod or running `go list -m all | grep excelize`
  2. 2. Update the dependency to version 2.11.0 or later using `go get github.com/xuri/excelize/[email protected]`
  3. 3. Run `go mod tidy` to clean up dependencies
  4. 4. Rebuild and redeploy the application
  5. 5. Test the application to ensure Excel file processing still functions correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Excelize Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54063 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54063 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data