CVE-2026-107224 json
Excelize: A Zip64 uncompressed-size of 2^63 panics OpenFile/OpenReader
published last mo. modified 4d ago also EUVD-2026-94555 , GHSA-fw94-4wwp-w8pw , GO-2026-6679
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.1.0 to 2.11.0, a Zip64 uncompressed size with the high bit set is converted from uint64 to a negative int64 before signed size-limit checks and allocation. ReadZipReader obtains UncompressedSize64 through FileInfo.Size and passes the wrapped negative value to readFile. When a crafted Zip64 entry declares an uncompressed size from 2^63 through 2^64-1 and the workbook is opened, the negative size bypasses unzip limits and reaches make as a negative capacity, allowing an attacker to panic during workbook opening. No fixed version is available as of this review.
Patch / fix
- go github.com/xuri/excelize/v2 2.11.1-0.20260805032953-db93f8d89de7
- github.com/qax-os/excelize@db93f8d commit
- github.com/qax-os/excelize#2369 pull request
Is CVE-2026-107224 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/qax-os/excelize/security/advisories/GHSA-fw94-4wwp-w8pw referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/xuri/excelize/v2 | >=2.1.0, <2.11.1-0.20260805032953-db93f8d89de7 <2.11.1-0.20260805032953-db93f8d89de7 |
2.11.1-0.20260805032953-db93f8d89de7 |
| go | github.com/360EntSecGroup-Skylar/excelize/v2 | >=2.1.0 |
no fix listed |
Affected products
- qax-os excelize
Classification
References
-
github.com
/qax-os/excelize/pull/2369
web, issue-tracking, patch
-
github.com
/qax-os/excelize/commit/db93f8d89de71589069a54d1b998af02e3c5f7cd
web, patch
-
github.com
/qax-os/excelize/security/advisories/GHSA-fw94-4wwp-w8pw
exploit, web, vendor-advisory, advisory
-
github.com
/qax-os/excelize
package
Sources
- CVE List CVE-2026-107224
- GitHub Advisory GHSA-fw94-4wwp-w8pw
- NVD CVE-2026-107224
- OSV GO-2026-6679
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.