ExcelJS prototype pollution in x14 conditional formatting merge
- Exploited
- Proof of concept public, per CISA
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
ExcelJS through 4.4.0 contains a prototype pollution vulnerability in mergeConditionalFormattings that allows attackers to modify Object.prototype by supplying an x14:cfRule id of __proto__. Attackers can craft an xlsx file that, when loaded with xlsx.load(), sets properties such as type, direction, border and cfvo on every object in the process until it restarts.
Who should check
Teams running exceljs 4.4.0 or earlier that load untrusted .xlsx files with xlsx.load(), including Node.js services and apps using the npm package
“Affecting exceljs <= 4.4.0”
What to do
Workaround: The checked facts name no workaround. The bug is triggered by loading a workbook that contains an x14:cfRule with id __proto__ through xlsx.load().
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-128337 (ExcelJS through 4.4.0 Prototype Pollution via x14 Conditional Formatting Rule ID), 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-128337 (entry last updated 2026-11-17):
Affected:
- npm package exceljs: through 4.4.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Workbook contains an x14:cfRule with id __proto__ (source: https://www.vulncheck.com/advisories/exceljs-through-4.4.0-prototype-pollution-via-x14-conditional-formatting-rule-id)
- Application loads the crafted .xlsx file with xlsx.load() (source: https://www.vulncheck.com/advisories/exceljs-through-4.4.0-prototype-pollution-via-x14-conditional-formatting-rule-id)
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-128337 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128337 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
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-86ch-m4gp-r5xf
- https://github.com/exceljs/exceljs/blob/v4.4.0/lib/xlsx/xform/sheet/worksheet-xform.js#L34-L42
- https://github.com/exceljs/exceljs/blob/v4.4.0/lib/xlsx/xform/sheet/worksheet-xform.js#L55-L74
- https://www.vulncheck.com/advisories/exceljs-through-4.4.0-prototype-pollution-via-x14-conditional-formatting-rule-id
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-128337
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-128337"}.Affected versions
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach20/20exceljs: 29M downloads a week
- Severity8.3/10CVSS 8.3
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 95 if added to CISA KEV
- Would score about 90 if CISA's SSVC rates exploitation active
- Would score about 70 if advisories confirm default setups are exposed
Impact
Timeline
- CVE published
- First seen by cve.now4 days
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Public exploit activity
- EPSS: 0.44%
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · mateocallec/exceljs-hardened · Advisory GHSA-86ch-m4gp-r5xf |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-128337 |
| Record | NVD · CVE-2026-128337 |
| Other links 4 | |
| Repository | GitHub · exceljs/exceljs · Repository |
| Repository | GitHub · exceljs/exceljs · lib/xlsx/xform/sheet/worksheet-xform.js · L34-L42 |
| Repository | GitHub · exceljs/exceljs · lib/xlsx/xform/sheet/worksheet-xform.js · L55-L74 |
| Link | vulncheck.com · advisories/exceljs-through-4.4.0-prototype-pollution-via-x14-conditional-formatting-rule-id |
Questions about CVE-2026-128337
Is CVE-2026-128337 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A crafted .xlsx workbook with an x14:cfRule whose id is __proto__ can set attacker-chosen properties such as type, direction and border on Object.prototype. Every object in the process then inherits those properties until it restarts.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-128337?
exceljs (npm): through 4.4.0.
Source: cve.now feed data
Am I affected, and how do I check?
ExcelJS through 4.4.0 is affected when the application loads a workbook with xlsx.load(). To check a project, look at the installed exceljs version in package.json or the output of npm ls exceljs.
Source: vulncheck.com, github.com
How do I fix CVE-2026-128337?
The checked facts do not name a fixed version or vendor patch, so no upgrade target can be given from them. Check the advisory for a patched release before relying on an update.
Source: vulncheck.com, github.com
What if there's no patch?
The checked facts name no workaround. The bug is triggered by loading a workbook that contains an x14:cfRule with id __proto__ through xlsx.load().
Source: vulncheck.com, github.com
Related
- CVE-2026-78207exceljs through 4.4.0 Prototype Pollution via deepMerge Reached From Note Serialization
- CVE-2026-128338ExcelJS through 4.4.0 Memory Exhaustion via Unbounded Worksheet Column Range
- CVE-2026-128339ExcelJS through 4.4.0 Memory Exhaustion via Oversized Merged Cell Range
- CVE-2026-128340ExcelJS through 4.4.0 Memory Exhaustion via Oversized Defined Name Range
- CVE-2026-128341ExcelJS through 4.4.0 Denial of Service via Oversized Data Validation sqref
- CVE-2026-128342ExcelJS through 4.4.0 Denial of Service via Oversized Worksheet sheetId
No corrections so far. Something wrong on this page? Report an error.