n8n before 1.123.85, 2.43.5, and 2.44.1 Stored XSS via Webhook Responses Missing Sandbox Policy
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.123.85, 2.44.1, 2.43.5
- 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
n8n, a workflow automation platform, is affected by this vulnerability in versions before the patched releases for its 1.x and 2.x lines. An authenticated user who can create and activate workflows could use webhook responses that lack the protective sandbox policy to serve malicious HTML, which runs with the session of anyone who opens the webhook URL.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
n8n before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1 contains a stored cross-site scripting vulnerability because some webhook response paths, such as error responses and responses without headers, omit the sandbox Content-Security-Policy. Authenticated members who can create and activate workflows can serve HTML that runs on the n8n origin, letting scripts act with the session of users who open the webhook URL.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- n8n-io n8n
fixed in 1.123.85
- n8n-io n8n
From 2.44.0 · fixed in 2.44.1
- n8n-io n8n
From 2.0.0 · fixed in 2.43.5