n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, an authenticated user with workflow edit access could configure a Respond to Webhook node to serve binary content with an attacker-controlled Content-Type. The binary response path bypassed the central Content-Security-Policy sandbox header, allowing a public webhook to execute JavaScript in the n8n origin when visited by an authenticated user, with access to that user's session. This vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.2.
CVE-2026-54301
MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(medium)
- EPSS
- 12.0%
- KEV
- Not listed
Published
June 16, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 23, 2026Patch available. Sources: github.
github Patch Available
Same-Origin XSS in Respond to Webhook Node · Advisory · n8n-io/n8n · GitHub
https://github.com/n8n-io/n8n/security/advisories/GHSA-v733-mwr6-fgcmVendor Advisories for CVE-2026-54301(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| n8n | — | 2.25.7 | — |
Frequently asked(5)
What is CVE-2026-54301?
CVE-2026-54301 is a medium vulnerability published on June 16, 2026. n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, an authenticated user with workflow edit access could configure a Respond to Webhook node to serve binary content with an attacker-controlled Content-Type. The binary response path bypassed the central…
When was CVE-2026-54301 disclosed?
CVE-2026-54301 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54301 actively exploited?
CVE-2026-54301 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54301?
CVE-2026-54301 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-54301?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54301, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54301
Is Your Infrastructure Affected by CVE-2026-54301?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.