High

n8n: Same-Origin XSS in Respond to Webhook Node

  • Disclosed: 16.06.2026
  • Updated: 11.10.2026 10:22

Impact

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.

Patches

The issue has been fixed in n8n versions 1.123.55, 2.25.7, and 2.26.2. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

  • Limit workflow creation and editing permissions to fully trusted users only.
  • Disable the Respond to Webhook node by adding n8n-nodes-base.respondToWebhook to the NODES_EXCLUDE environment variable.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package n8n < 1.123.55, >= 2.26.0, < 2.26.2, >= 2.0.0-rc.0, < 2.25.7 1.123.55, 2.26.2, 2.25.7

References

CVSS score 7.6/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
Weakness (CWE)
CWE-79
Platform
npm
Package
n8n
Disclosed
16.06.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-v733-mwr6-fgcm - CC BY 4.0

Vulnerability history: n8n

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (156) in the archive
Total entries
156
First → latest
05.2023 09.2026
Without a fix
1
Exploited in attacks
1

Severity breakdown

  • Critical 24
  • High 58
  • Medium 74

Disclosures per year

  1. 2023: 3
  2. 2024: 0
  3. 2025: 14
  4. 2026: 139
Severity:
  1. High CVE-2026-86083 < 1.123.76, >= 2.38.0, < 2.38.2, >= 2.0.0, < 2.37.7 1.123.76, 2.38.2, 2.37.7
  2. High CVE-2026-86082 < 1.123.76, >= 2.38.0, < 2.38.2, >= 2.0.0, < 2.37.7 1.123.76, 2.38.2, 2.37.7
  3. High CVE-2026-86081 < 1.123.76, >= 2.38.0, < 2.38.2, >= 2.0.0, < 2.37.7 1.123.76, 2.38.2, 2.37.7
  4. High CVE-2026-86075 >= 2.38.0, < 2.38.2, < 2.37.7 2.38.2, 2.37.7
  5. High CVE-2026-86076 < 1.123.76, >= 2.38.0, < 2.38.2, >= 2.0.0, < 2.37.7 1.123.76, 2.38.2, 2.37.7
  6. High CVE-2026-72749 < 1.123.67, >= 2.32.0, < 2.32.1, >= 2.0.0-rc.0, < 2.31.5 1.123.67, 2.32.1, 2.31.5
  7. High CVE-2026-72762 < 1.123.67, >= 2.32.0, < 2.32.1, >= 2.0.0-rc.0, < 2.31.5 1.123.67, 2.32.1, 2.31.5
  8. High CVE-2026-72763 < 1.123.67, >= 2.32.0, < 2.32.1, >= 2.0.0-rc.0, < 2.31.5 1.123.67, 2.32.1, 2.31.5
  9. High CVE-2026-72774 < 1.123.67, >= 2.32.0, < 2.32.1, >= 2.0.0-rc.0, < 2.31.5 1.123.67, 2.32.1, 2.31.5
  10. High CVE-2026-72765 >= 2.32.0, < 2.32.1, < 2.31.5 2.32.1, 2.31.5
  11. High CVE-2026-72766 < 1.123.67, >= 2.32.0, < 2.32.1, >= 2.0.0-rc.0, < 2.31.5 1.123.67, 2.32.1, 2.31.5
  12. High CVE-2026-72767 < 1.123.67, >= 2.32.0, < 2.32.1, >= 2.0.0-rc.0, < 2.31.5 1.123.67, 2.32.1, 2.31.5
  13. High CVE-2026-72770 < 1.123.67, >= 2.32.0, < 2.32.1, >= 2.0.0-rc.0, < 2.31.5 1.123.67, 2.32.1, 2.31.5
  14. High CVE-2026-72771 >= 2.32.0, < 2.32.1, < 2.31.5 2.32.1, 2.31.5
  15. High CVE-2026-72772 >= 2.32.0, < 2.32.1, < 2.31.5 2.32.1, 2.31.5
  16. High CVE-2026-65016 < 1.123.64, >= 2.30.0, < 2.30.1, >= 2.0.0-rc.0, < 2.29.8 1.123.64, 2.30.1, 2.29.8
  17. High CVE-2026-65591 < 1.123.64, >= 2.30.0, < 2.30.1, >= 2.0.0-rc.0, < 2.29.8 1.123.64, 2.30.1, 2.29.8
  18. High CVE-2026-59208 >= 2.28.0, < 2.28.1, < 2.27.4 2.28.1, 2.27.4
  19. High CVE-2026-59207 >= 2.28.0, < 2.28.1, < 2.27.4 2.28.1, 2.27.4
  20. High CVE-2026-59206 < 1.123.61, >= 2.28.0, < 2.28.1, >= 2.0.0-rc.0, < 2.27.4 1.123.61, 2.28.1, 2.27.4
  21. High CVE-2026-59209 < 1.123.61, >= 2.28.0, < 2.28.1, >= 2.0.0-rc.0, < 2.27.4 1.123.61, 2.28.1, 2.27.4
  22. High CVE-2026-65592 < 1.123.64, >= 2.30.0, < 2.30.1, >= 2.0.0-rc.0, < 2.29.8 1.123.64, 2.30.1, 2.29.8
  23. High CVE-2026-65597 < 1.123.64, >= 2.30.0, < 2.30.1, >= 2.0.0-rc.0, < 2.29.8 1.123.64, 2.30.1, 2.29.8
  24. High CVE-2026-65598 < 1.123.64, >= 2.30.0, < 2.30.1, >= 2.0.0-rc.0, < 2.29.8 1.123.64, 2.30.1, 2.29.8
  25. High CVE-2026-65015 >= 2.30.0, < 2.30.1, < 2.29.8 2.30.1, 2.29.8
  26. High · 7.7 CVE-2026-54304 < 1.123.55, >= 2.26.0, < 2.26.1, >= 2.0.0-rc.0, < 2.25.7 1.123.55, 2.26.1, 2.25.7
  27. High · 10.0 CVE-2026-54309 >= 2.26.0, < 2.26.2, < 2.25.7 2.26.2, 2.25.7
  28. High · 9.9 CVE-2026-54305 < 1.123.55, >= 2.26.0, < 2.26.2, >= 2.0.0-rc.0, < 2.25.7 1.123.55, 2.26.2, 2.25.7
  29. High · 9.6 CVE-2026-54307 < 1.123.55, >= 2.26.0, < 2.26.2, >= 2.0.0-rc.0, < 2.25.7 1.123.55, 2.26.2, 2.25.7
  30. High · 7.6 CVE-2026-54302 < 1.123.55, >= 2.26.0, < 2.26.2, >= 2.0.0-rc.0, < 2.25.7 1.123.55, 2.26.2, 2.25.7
  31. High · 8.5 CVE-2026-54312 < 2.24.0 2.24.0
  32. n8n: Same-Origin XSS in Respond to Webhook Node this entry
    High · 7.6 CVE-2026-54301 < 1.123.55, >= 2.26.0, < 2.26.2, >= 2.0.0-rc.0, < 2.25.7 1.123.55, 2.26.2, 2.25.7
  33. High · 8.5 CVE-2026-49444 < 1.123.48, >= 2.22.0, < 2.22.4, >= 2.0.0-rc.0, < 2.21.8 1.123.48, 2.22.4, 2.21.8
  34. High · 8.1 CVE-2026-45732 < 1.123.43, >= 2.21.0, < 2.21.1, >= 2.0.0-rc.0, < 2.20.7 1.123.43, 2.21.1, 2.20.7
  35. High · 9.0 CVE-2026-44792 < 1.123.43, >= 2.21.0, < 2.21.1, >= 2.0.0-rc.0, < 2.20.7 1.123.43, 2.21.1, 2.20.7
  36. Critical · 9.9 CVE-2026-44791 < 1.123.43, >= 2.21.0, < 2.22.1, >= 2.0.0-rc.0, < 2.20.7 1.123.43, 2.22.1, 2.20.7
  37. Critical · 8.8 CVE-2026-44790 < 1.123.43, >= 2.21.0, < 2.22.1, >= 2.0.0-rc.0, < 2.20.7 1.123.43, 2.22.1, 2.20.7
  38. Critical · 9.9 CVE-2026-44789 < 1.123.43, >= 2.21.0, < 2.22.1, >= 2.0.0-rc.0, < 2.20.7 1.123.43, 2.22.1, 2.20.7
  39. Critical · 9.9 CVE-2026-42232 >= 2.18.0, < 2.18.1, >= 2.17.0, < 2.17.4, < 1.123.32 2.18.1, 2.17.4, 1.123.32
  40. Critical · 10.0 CVE-2026-42231 < 1.123.32, >= 2.18.0, < 2.18.1, >= 2.17.0, < 2.17.4 1.123.32, 2.18.1, 2.17.4
  41. High · 8.2 CVE-2026-42235 < 1.123.32, >= 2.18.0, < 2.18.1, >= 2.17.0, < 2.17.4 1.123.32, 2.18.1, 2.17.4
  42. High · 8.5 CVE-2026-42226 >= 2.17.0, < 2.17.5, < 1.123.33 2.17.5, 1.123.33
  43. High · 7.5 CVE-2026-42234 < 1.123.32, >= 2.18.0, < 2.18.1, >= 2.17.0, < 2.17.4 1.123.32, 2.18.1, 2.17.4
  44. High · 7.5 CVE-2026-42236 < 1.123.32, >= 2.18.0, < 2.18.1, >= 2.0.0, < 2.17.4 1.123.32, 2.18.1, 2.17.4
  45. High · 9.9 CVE-2026-33713 < 1.123.26, >= 2.14.0, < 2.14.1, >= 2.0.0-rc.0, < 2.13.3 1.123.26, 2.14.1, 2.13.3
  46. Critical · 9.9 CVE-2026-33696 >= 2.14.0, < 2.14.1, >= 2.0.0-rc.0, < 2.13.3, < 1.123.27 2.14.1, 2.13.3, 1.123.27
  47. High · 6.3 CVE-2026-33722 < 1.123.23, >= 2.0.0-rc.0, < 2.6.4 1.123.23, 2.6.4
  48. High · 8.2 CVE-2026-33665 >= 2.0.0-rc.0, < 2.4.0, < 1.121.0 2.4.0, 1.121.0
  49. High · 9.9 CVE-2026-33663 < 1.123.27, >= 2.14.0, < 2.14.1, >= 2.0.0-rc.0, < 2.13.3 1.123.27, 2.14.1, 2.13.3
  50. Critical · 9.9 CVE-2026-33660 >= 2.14.0, < 2.14.1, >= 2.0.0-rc.0, < 2.13.3, < 1.123.27 2.14.1, 2.13.3, 1.123.27
  51. High · 6.5 CVE-2026-27496 < 1.123.22, >= 2.10.0, < 2.10.1, >= 2.0.0-rc.0, < 2.9.3 1.123.22, 2.10.1, 2.9.3
  52. High · 5.4 CVE-2026-27578 < 1.123.22, >= 2.0.0, < 2.9.3, >= 2.10.0, < 2.10.1 1.123.22, 2.9.3, 2.10.1
  53. Critical · 9.9 CVE-2026-27577 < 1.123.22, >= 2.0.0, < 2.9.3, >= 2.10.0, < 2.10.1 1.123.22, 2.9.3, 2.10.1
  54. Critical · 8.5 CVE-2026-27498 < 1.123.8, >= 2.0.0, < 2.2.0 1.123.8, 2.2.0
  55. Critical · 9.9 CVE-2026-27497 < 1.123.22, >= 2.0.0, < 2.9.3, >= 2.10.0, < 2.10.1 1.123.22, 2.9.3, 2.10.1
  56. Critical CVE-2026-27495 < 1.123.22, >= 2.0.0, < 2.9.3, >= 2.10.0, < 2.10.1 1.123.22, 2.9.3, 2.10.1
  57. High · 9.9 CVE-2026-27494 < 1.123.22, >= 2.0.0, < 2.9.3, >= 2.10.0, < 2.10.1 1.123.22, 2.9.3, 2.10.1
  58. Critical · 9.0 CVE-2026-27493 < 1.123.22, >= 2.0.0, < 2.9.3, >= 2.10.0, < 2.10.1 1.123.22, 2.9.3, 2.10.1
  59. Critical · 9.9 CVE-2026-25115 < 2.4.8 2.4.8
Show more (20) Showing 60 of 82

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.