CVE
ExcelJS denial of service via oversized row numbers in XLSX parsing
Affects ExcelJS through 4.4.0 in applications that load XLSX files and then call getSheetValues(), write the workbook, or export CSV. No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Do first: Workaround: The checked facts give no workaround. Until a fix is available, avoid loading XLSX files from untrusted sources, or limit the features that process them, since the trigger requires the application to load such a file.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.68% · 53rd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
exceljs through 4.4.0 contains a denial of service vulnerability that allows attackers to block the event loop by supplying unbounded row r attributes parsed in row-xform.js. Attackers can craft an XLSX file with a row numbered far beyond Excel's limit, making getSheetValues(), workbook writes and CSV export consume time proportional to that number.
Who should check
Teams running exceljs through 4.4.0 that load untrusted XLSX files and call getSheetValues(), workbook writes or CSV export.
Read the source excerpt
“exceljs through 4.4.0 contains a denial of service vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts give no workaround. Until a fix is available, avoid loading XLSX files from untrusted sources, or limit the features that process them, since the trigger requires the application to load such a file.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128343 (ExcelJS through 4.4.0 Denial of Service via Oversized Row Number), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128343 (entry last updated 2026-11-13):
Affected:
- exceljs exceljs: through 4.4.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The application loads an XLSX file that an attacker can craft, containing a row numbered far beyond Excel's limit. (source: https://www.vulncheck.com/advisories/exceljs-through-4.4.0-denial-of-service-via-oversized-row-number)
- The application calls getSheetValues(), writes the workbook, or exports CSV after loading that file. (source: https://www.vulncheck.com/advisories/exceljs-through-4.4.0-denial-of-service-via-oversized-row-number)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-128343 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128343 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/exceljs/exceljs
- https://github.com/mateocallec/exceljs-hardened/security/advisories/GHSA-3gm5-qxj8-89rr
- https://github.com/exceljs/exceljs/blob/v4.4.0/lib/xlsx/xform/sheet/row-xform.js#L73-L77
- https://github.com/exceljs/exceljs/blob/v4.4.0/lib/doc/worksheet.js#L886-L893
- https://github.com/exceljs/exceljs/blob/v4.4.0/lib/doc/worksheet.js#L571-L580
- https://www.vulncheck.com/advisories/exceljs-through-4.4.0-denial-of-service-via-oversized-row-number
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128343
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128343"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- exceljs exceljs
through 4.4.0
Evidence 8
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Repository
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128343
Is CVE-2026-128343 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted XLSX file can contain a row numbered far beyond Excel's limit. Processing that file with getSheetValues(), workbook writes, or CSV export takes time that grows with that row number, which can block the Node.js event loop.Source: vulncheck.com
Which versions are affected by CVE-2026-128343?
exceljs: through 4.4.0.Source: cve.now feed data
Am I affected, and how do I check?
ExcelJS versions through 4.4.0 are affected. To check, run npm ls exceljs in the project, then see whether the application loads XLSX files that could come from an untrusted source and calls getSheetValues(), writes the workbook, or exports CSV.Source: vulncheck.com
How do I fix CVE-2026-128343?
The checked facts do not name a fixed version or vendor patch, so no upgrade target can be given here. Check the ExcelJS advisory or release notes for a fixed release newer than 4.4.0.Source: vulncheck.com
What if there's no patch?
The checked facts give no workaround. Until a fix is available, avoid loading XLSX files from untrusted sources, or limit the features that process them, since the trigger requires the application to load such a file.Source: vulncheck.com