A significant security flaw has been identified in N8N, a popular tool for automating workflows. This vulnerability, tracked as CVE-2025-56265, affects the “Chat Trigger” component. Simply put, it allows attackers to upload dangerous files, such as specially crafted HTML documents. When another user interacts with or previews these files, the malicious code within them can run in their web browser. This type of attack, known as Stored Cross-Site Scripting (XSS), could lead to severe outcomes like unauthorized access to accounts or the theft of sensitive data.
CVE Details
This vulnerability impacts specific versions of the N8N application, making it crucial for users to understand its specifics.
- Product: N8N
- Published: September 8, 2025
- Last Modified: November 7, 2026
- Severity: High (CVSS score: 8.8)
- Status: Analyzed
Affected Products
The arbitrary file upload vulnerability is found in the Chat Trigger component across the following N8N versions:
- N8N v1.95.3
- N8N v1.100.1
- N8N v1.101.1
Current Status
The vulnerability, CVE-2025-56265, is currently listed with an “Analyzed” status. This means that its details have been thoroughly examined and made public. If you are using any of the affected versions, it is highly recommended to take immediate action to mitigate the potential risks.
Severity Level
This vulnerability is classified as HIGH severity, scoring 8.8 on the CVSS scale. A high rating signifies that successful exploitation of this flaw could have a critical impact on your N8N instance and its users. The ability for an attacker to upload arbitrary files and execute code can lead to significant control over the system, compromise user accounts, and facilitate the exfiltration of confidential information.
Possible Solutions
While official patches from N8N for this specific vulnerability may be forthcoming, there are several essential steps you can take right now to protect your systems:
- Restrict Allowed File Types: Configure your N8N environment to only accept safe, non-executable file formats for uploads. This means actively rejecting file extensions like
.html,.js,.svg, and any others that can contain or execute active scripts. - Implement Robust Content Validation: Beyond just checking file extensions, it’s vital to perform server-side validation of the actual content of uploaded files. This helps ensure that no embedded scripts or other malicious code are present. For instance, when uploading images, verify their MIME types and “magic numbers” to confirm they are indeed legitimate image files.
- Isolate User Uploads with a Content Security Policy (CSP): A critical security practice is to serve all user-uploaded content from a completely separate domain or Content Delivery Network (CDN). This isolation is fundamental for enforcing a strong Content Security Policy (CSP), which prevents malicious scripts from interacting with your main application domain.
- Configure Secure HTTP Headers: Set appropriate HTTP headers for all content served, especially for uploaded files. Important headers include:
Content-Type: Ensure this header accurately reflects the file’s true type.X-Content-Type-Options: nosniff: This header prevents browsers from guessing the MIME type of content, thereby mitigating risks if a file with an incorrect MIME type is accidentally executed.- A comprehensive
Content Security Policy (CSP): This header allows you to define which web resources (like scripts, stylesheets, and images) a browser is permitted to load or execute, effectively blocking potential inline scripts used in XSS attacks.
References
https://github.com/nikolas-ch/CVEs/blob/main/N8N/N8N_v1.100.1/ChatTrigger_StoredXSSviaUnrestrictedFileUpload/StoredXSSviaUnristrictedFileUpload.txt
https://github.com/nikolas-ch/CVEs/tree/main/N8N/N8N_v1.100.1
https://github.com/nikolas-ch/CVEs/tree/main/N8N/N8N_v1.100.1/ChatTrigger_StoredXSSviaUnrestrictedFileUpload