Skip to content

Commit 585556e

Browse files
committed
1 parent 869d274 commit 585556e

1 file changed

Lines changed: 2 additions & 6 deletions

File tree

advisories/github-reviewed/2026/03/GHSA-3c7f-5hgj-h279/GHSA-3c7f-5hgj-h279.json

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,12 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-3c7f-5hgj-h279",
4-
"modified": "2026-03-27T18:06:49Z",
4+
"modified": "2026-03-27T18:06:50Z",
55
"published": "2026-03-27T18:06:49Z",
66
"aliases": [],
77
"summary": "n8n has XSS in Chat Trigger Node through Custom CSS",
88
"details": "## Impact\nAn authenticated user with permission to create or modify workflows could inject malicious JavaScript into the Custom CSS field of the Chat Trigger node. Due to a misconfiguration in the `sanitize-html` library, the sanitization could be bypassed, resulting in stored XSS on the public chat page. Any user visiting the chat URL would be affected.\n\n## Patches\nThe issue has been fixed in n8n versions 1.123.27, 2.13.3, and 2.14.1. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Limit workflow creation and editing permissions to fully trusted users only.\n- Disable the Chat Trigger node by adding `@n8n/n8n-nodes-langchain.chatTrigger` to the `NODES_EXCLUDE` environment variable.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
99
"severity": [
10-
{
11-
"type": "CVSS_V3",
12-
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N"
13-
},
1410
{
1511
"type": "CVSS_V4",
1612
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N"
@@ -49,7 +45,7 @@
4945
"introduced": "2.14.0"
5046
},
5147
{
52-
"fixed": "2..14.1"
48+
"fixed": "2.14.1"
5349
}
5450
]
5551
}

0 commit comments

Comments
 (0)