CVE-2026-107219 json
Excelize: Unbounded spinCount in agile decryption burns CPU during OpenFile
published last mo. modified 4d ago also EUVD-2026-94549 , GHSA-jrfj-fhj2-jjvm , GO-2026-6681
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.3.1 to 2.11.0, agile decryption accepts an attacker-controlled spinCount and performs that many password-key derivation iterations before verifier validation. OpenFile reaches agileDecrypt, which passes the unbounded spinCount to convertPasswdToKey before password verification. When a crafted OLE encrypted-workbook header supplies an excessive spinCount and the file is opened, the key-derivation loop performs unbounded attacker-selected work and cannot be cancelled, allowing an attacker to consume a CPU core for an attacker-controlled duration. No fixed version is available as of this review.
Patch / fix
- go github.com/xuri/excelize/v2 2.11.1-0.20260906004932-2badfcd5841d
- github.com/qax-os/excelize@2badfcd commit
- github.com/qax-os/excelize#2389 pull request
Is CVE-2026-107219 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
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/qax-os/excelize/security/advisories/GHSA-jrfj-fhj2-jjvm referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/xuri/excelize/v2 | >=2.3.1, <2.11.1-0.20260906004932-2badfcd5841d <2.11.1-0.20260906004932-2badfcd5841d |
2.11.1-0.20260906004932-2badfcd5841d |
| go | github.com/360EntSecGroup-Skylar/excelize/v2 | >=2.3.1 |
no fix listed |
Affected products
- qax-os excelize
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
github.com
/qax-os/excelize/pull/2389
web, issue-tracking, patch
-
github.com
/qax-os/excelize/commit/2badfcd5841d0d88b0ffea119f5a2f3c53b4910b
web, patch
-
github.com
/qax-os/excelize/security/advisories/GHSA-jrfj-fhj2-jjvm
web, exploit, vendor-advisory, advisory
-
github.com
/qax-os/excelize
package
Sources
- CVE List CVE-2026-107219
- GitHub Advisory GHSA-jrfj-fhj2-jjvm
- NVD CVE-2026-107219
- OSV GO-2026-6681
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.