Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-21858: CWE-20: Improper Input Validation in n8n-io n8n

0
Critical
VulnerabilityCVE-2026-21858cvecve-2026-21858cwe-20
Published: Wed Jan 07 2026 (01/07/2026, 23:57:52 UTC)
Source: CVE Database V5
Vendor/Project: n8n-io
Product: n8n

Description

n8n is an open source workflow automation platform. Versions starting with 1.65.0 and below 1.121.0 enable an attacker to access files on the underlying server through execution of certain form-based workflows. A vulnerable workflow could grant access to an unauthenticated remote attacker, resulting in exposure of sensitive information stored on the system and may enable further compromise depending on deployment configuration and workflow usage. This issue is fixed in version 1.121.0.

AI-Powered Analysis

AILast updated: 01/08/2026, 00:24:39 UTC

Technical Analysis

CVE-2026-21858 is a critical security vulnerability found in the open-source workflow automation platform n8n, affecting all versions prior to 1.121.0. The root cause is improper input validation (CWE-20) in certain form-based workflows, which allows an unauthenticated remote attacker to execute crafted inputs that access files on the underlying server. This flaw essentially enables attackers to bypass authentication and retrieve sensitive files, potentially including configuration files, credentials, or other confidential data stored on the system. The vulnerability can also facilitate further compromise depending on how the workflows are deployed and the nature of the data processed. The CVSS v3.1 base score is 10.0, reflecting the highest severity due to network attack vector, no required privileges, no user interaction, and complete impact on confidentiality and integrity, though availability is not affected. The vulnerability was publicly disclosed on January 7, 2026, and fixed in n8n version 1.121.0. No public exploits have been reported yet, but the critical nature and ease of exploitation make it a significant threat. Organizations using n8n should prioritize upgrading to the patched version and audit their workflow configurations to ensure no vulnerable workflows remain active. Additionally, limiting network exposure of n8n instances and implementing strict access controls can reduce risk.

Potential Impact

For European organizations, this vulnerability poses a severe risk of data breach and unauthorized access to sensitive information managed within n8n workflows. Given n8n’s role in automating business processes, exposure of internal files could lead to leakage of intellectual property, customer data, or credentials, potentially enabling lateral movement or further attacks within the network. Organizations in sectors such as finance, healthcare, manufacturing, and government, which often rely on automation platforms and handle sensitive data, are particularly vulnerable. The critical severity and unauthenticated remote exploitability mean that attackers can compromise systems without insider access or user interaction, increasing the likelihood of rapid exploitation. This could disrupt business operations, damage reputation, and incur regulatory penalties under GDPR if personal data is exposed. The impact is magnified in environments where n8n is integrated with other critical systems or cloud services, as attackers could leverage the initial access to escalate privileges or pivot to other assets.

Mitigation Recommendations

1. Immediately upgrade all n8n instances to version 1.121.0 or later to apply the official patch addressing CVE-2026-21858. 2. Conduct a thorough audit of all existing workflows, especially those involving form inputs, to identify and disable any potentially vulnerable workflows until patched. 3. Restrict network access to n8n instances by implementing firewall rules, VPNs, or zero-trust network segmentation to limit exposure to trusted users and systems only. 4. Implement strong authentication and authorization controls on n8n, even though the vulnerability allows unauthenticated access, to reduce attack surface and monitor for suspicious activity. 5. Monitor logs and network traffic for unusual file access patterns or attempts to exploit form inputs. 6. Educate development and operations teams about secure workflow design and input validation best practices to prevent similar issues. 7. Consider deploying web application firewalls (WAFs) with custom rules to detect and block malicious payloads targeting form inputs. 8. Regularly review and update incident response plans to include scenarios involving workflow automation platform compromises.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-05T16:44:16.367Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695ef5ea07b8a419a7738b33

Added to database: 1/8/2026, 12:10:18 AM

Last enriched: 1/8/2026, 12:24:39 AM

Last updated: 1/9/2026, 2:05:36 AM

Views: 31

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats