ExcelJS CVE-2026-128347: file read through addImage, no upstream fix

Updated 2026-11-15

Short answer: CVE-2026-128347 affects every exceljs release through 4.4.0, which is still the newest version on npm (published 19 October 2023). If an app passes a filename that a user controls to addImage in the streaming WorkbookWriter, a name with ../ segments makes ExcelJS copy any file the Node.js process can read into the workbook under xl/media (NVD, VulnCheck). As of 15 November 2026 there is no fixed exceljs release.

Facts

CVECVE-2026-128347, arbitrary file read via WorkbookWriter addImage filename
Affectedexceljs 4.4.0 and earlier (NVD, VulnCheck)
Fixed inNo upstream release. Latest on npm: 4.4.0; the only later build is 4.4.1-prerelease.0 from 20 December 2024, which no advisory mentions
ScoreCVSS 4.0 8.7 (VulnCheck), CVSS 3.1 7.5 (NVD)
WeaknessCWE-73, external control of file name or path
PublishedVulnCheck 12 November 2026, NVD 13 November 2026
ExploitedNot in CISA's exploited list (13 November 2026 catalog)
CreditMatéo Florian Callec (VulnCheck)

Who is affected

An app is exposed when three things are true: it uses exceljs 4.4.0 or older, it writes files with the streaming writer (ExcelJS.stream.xlsx.WorkbookWriter), and a path that comes from user input reaches addImage. The read file ends up inside the workbook the app hands back, so whoever downloads the workbook gets the file. The proof of concept in the finder's advisory embeds /etc/hostname as xl/media/image0.png. A spreadsheet that only uses images your own code chooses is not exposed this way.

Where the advisory comes from

The GitHub advisory NVD links, GHSA-f9m8-8qmf-qq29, was published on 16 October 2026 in exceljs-hardened, an "unofficial security-hardened fork of exceljs" that says it is "not affiliated with the original exceljs maintainers" (npm). That advisory lists exceljs-hardened 5.1.0 as patched. It does not cover the exceljs package. GitHub's own entry for the CVE, GHSA-jf4h-9vf8-6gmp, is unreviewed and names no patched version.

Check your projects (read-only)

npm ls exceljs --all
pnpm why exceljs
yarn why exceljs
grep -rnE 'WorkbookWriter|addImage' --include=*.js --include=*.ts --include=*.mjs --exclude-dir=node_modules .

The first three show every installed copy, including ones pulled in by other packages. The grep finds the code that uses the streaming writer or adds images, so you can see where each filename comes from. None of these commands changes anything.

FixLane's page: ExcelJS lets crafted addImage paths read any local file. NVD's facts: CVE-2026-128347.

Questions

Is there a fixed version of exceljs?

No. As of 15 November 2026 the newest exceljs on npm is 4.4.0 from October 2023, and NVD lists everything through 4.4.0 as affected. The only patched release named in an advisory is 5.1.0 of the unofficial fork exceljs-hardened.

Does CVE-2026-128347 affect every app that uses ExcelJS?

No. It needs the streaming WorkbookWriter and a filename from user input passed to addImage. Then any file the Node.js process can read can end up in the generated workbook.

How do I find out if my project uses exceljs?

Run npm ls exceljs --all (or pnpm why exceljs, yarn why exceljs). It lists direct and transitive copies with their versions.

Sources

Check your own machine

Connect an AI agent to the free, read-only FixLane MCP server or ask the Telegram bot: it checks what you have installed against verified fixed versions and serves a reviewed fix procedure. All guides.