PT-2026-50169 · Npm · N8N
Published
2026-06-16
·
Updated
2026-06-16
·
CVE-2026-54303
CVSS v3.1
7.6
High
| Vector | AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N |
Impact
An endpoint in the Meta and Microsoft Teams trigger nodes reflects a query parameter into the HTTP response without sanitization or Content-Security-Policy headers, enabling reflected XSS in the n8n origin when a logged-in user visits a crafted URL.
Patches
The issue has been fixed in n8n version 2.24.0. Users should upgrade to this version or later to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and activation permissions to fully trusted users only.
- Disable the affected nodes by adding
n8n-nodes-base.facebookTrigger,n8n-nodes-base.whatsAppTrigger,n8n-nodes-base.facebookLeadAdsTrigger, andn8n-nodes-base.microsoftTeamsTriggerto theNODES EXCLUDEenvironment variable.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Fix
XSS
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
N8N