GHSA-58jc-rcg5-95f3
HIGHn8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
n8nnpmDescription
Summary
A stored Cross-Site Scripting (XSS) vulnerability may occur in n8n when using the “Respond to Webhook” node. When this node responds with HTML content containing executable scripts, the payload may execute directly in the top-level window, rather than within the expected sandbox introduced in version 1.103.0.
This behavior can enable a malicious actor with workflow creation permissions to execute arbitrary JavaScript in the context of the n8n editor interface.
While session cookies (n8n-auth) are marked HttpOnly and cannot be directly exfiltrated, the vulnerability can facilitate Cross-Site Request Forgery (CSRF)-like actions from within the user’s authenticated session, potentially allowing:
- Unauthorized reading of sensitive workflow data or execution history.
- Unauthorized modification or deletion of workflows.
- Insertion of malicious workflow logic or external data exfiltration steps.
n8n instances that allow untrusted users to create workflows are particularly impacted.
Patches
The vulnerability has been patched in v.1.114.0.
Workarounds
- Restrict workflow creation and modification privileges to trusted users only.
- Avoid using untrusted HTML responses in the “Respond to Webhook” node.
- Use an external reverse proxy or HTML sanitizer to filter responses that include executable scripts.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | n8n | all versions | 1.114.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update n8n to 1.114.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-58jc-rcg5-95f3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-58jc-rcg5-95f3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-58jc-rcg5-95f3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-58jc-rcg5-95f3 in your dependencies?
O3 detects GHSA-58jc-rcg5-95f3 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.