CVE
ExcelJS arbitrary file read in WorkbookWriter addImage
Affects exceljs 4.4.0 and earlier when the streaming WorkbookWriter passes image paths built from user-controlled input to addImage. No fixed version is listed.
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 name no fix and no workaround. Limiting the affected feature means not building addImage paths from user-controlled input when using the streaming WorkbookWriter.
- 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.51% · 43rd 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 an arbitrary file read vulnerability in the streaming WorkbookWriter that allows attackers to read local files by supplying crafted image filenames to addImage. Attackers can inject ../ path segments into user-controlled image paths, causing addMedia to embed any file readable by the Node.js process under xl/media in the generated workbook.
Who should check
Teams using exceljs 4.4.0 or earlier with the streaming WorkbookWriter, where user input can reach addImage image filenames.
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 name no fix and no workaround. Limiting the affected feature means not building addImage paths from user-controlled input when using the streaming WorkbookWriter.
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-128347 (ExcelJS through 4.4.0 Arbitrary File Read via WorkbookWriter addImage Filename), 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-128347 (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):
- ExcelJS 4.4.0 or earlier (source: https://www.vulncheck.com/advisories/exceljs-through-4.4.0-arbitrary-file-read-via-workbookwriter-addimage-filename)
- Uses the streaming WorkbookWriter (source: https://www.vulncheck.com/advisories/exceljs-through-4.4.0-arbitrary-file-read-via-workbookwriter-addimage-filename)
- Image file paths built from user-controlled input are passed to addImage (source: https://www.vulncheck.com/advisories/exceljs-through-4.4.0-arbitrary-file-read-via-workbookwriter-addimage-filename)
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-128347 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128347 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-f9m8-8qmf-qq29
- https://github.com/exceljs/exceljs/blob/v4.4.0/lib/stream/xlsx/workbook-writer.js#L230-L237
- https://github.com/exceljs/exceljs/blob/v4.4.0/lib/stream/xlsx/workbook-writer.js#L124-L130
- https://www.vulncheck.com/advisories/exceljs-through-4.4.0-arbitrary-file-read-via-workbookwriter-addimage-filename
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-128347
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-128347"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- exceljs exceljs
through 4.4.0
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- 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-128347
Is CVE-2026-128347 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?
Crafted image filenames containing ../ path segments can make ExcelJS read local files that the Node.js process can read. The file contents are then embedded in the generated workbook under xl/media.Source: vulncheck.com
Which versions are affected by CVE-2026-128347?
exceljs: through 4.4.0.Source: cve.now feed data
Am I affected, and how do I check?
ExcelJS 4.4.0 or earlier is affected when the streaming WorkbookWriter is used and image paths built from user-controlled input are passed to addImage. To check, run npm ls exceljs in the project to see the installed version, and look for WorkbookWriter calls to addImage that take user-supplied paths.Source: vulncheck.com
How do I fix CVE-2026-128347?
The checked facts list no fixed version and no vendor patch ids, so no upgrade target can be given from them.Source: vulncheck.com
What if there's no patch?
The checked facts name no fix and no workaround. Limiting the affected feature means not building addImage paths from user-controlled input when using the streaming WorkbookWriter.Source: vulncheck.com