Skip to content
Blog

n8n Unauthorized Workflow Manipulation Vulnerability (CVE-2026-42228) — Moderate Severity

N8N-Banner-ucartz
In this article
  1. CVE Details
  2. Affected Products
  3. Current Status
  4. Severity Level
  5. Possible Solutions
  6. References

n8n is a powerful open-source platform designed to automate workflows, helping users connect various applications and services. However, a recent security flaw, identified as CVE-2026-42228, has been discovered in the platform, allowing unauthorized individuals to potentially interfere with ongoing workflows.

This vulnerability specifically impacts the Chat Trigger node’s Hosted Chat feature. Under certain conditions, an attacker could gain unauthorized access to an active workflow, read sensitive prompts, and even inject their own input to alter the workflow’s intended path or trigger unintended actions.

CVE Details

Product: n8n workflow automation platform
Published: May 4, 2026
Severity: Moderate
Status: Analyzed

Affected Products

This vulnerability affects specific versions of the n8n platform. Installations running versions prior to 1.123.32, 2.17.4, and 2.18.1 are at risk. It’s important for users to check their current n8n version to determine if their setup is vulnerable.

Current Status

The vulnerability, CVE-2026-42228, has been analyzed, and its details, including impact and potential solutions, have been publicly disclosed. Patches are available to address the issue.

Severity Level

Rated as “Moderate” (CVSS 6.3), this vulnerability poses a significant risk. The main concern is the potential for unauthorized workflow manipulation. An attacker could, without proper authentication, tap into a workflow execution, observe sensitive information (like prompts intended for legitimate users), and then supply arbitrary input. This could lead to data exposure, unauthorized actions, or disruption of automated processes, impacting both the confidentiality and integrity of the affected workflows.

For an attack to be successful, three key conditions must be met:

  • The n8n instance must have a public Hosted Chat workflow with authentication set to “None.”
  • A target workflow execution must be in a “waiting” state at the time of the attack.
  • The attacker needs to obtain or discover the specific execution ID of that waiting workflow.

Possible Solutions

Immediate action is recommended to mitigate the risks associated with this vulnerability:

  • Upgrade Immediately: The most effective solution is to upgrade your n8n installation to a patched version. This includes versions 1.123.32, 2.17.4, 2.18.1, or any later releases. These versions contain the necessary fixes to prevent unauthorized access to the /chat WebSocket endpoint.
  • Temporary Workaround: If an immediate upgrade is not feasible, administrators can apply a temporary mitigation. Ensure that all Chat Trigger nodes have their “Authentication” field set to “n8n User Auth” instead of “None.” It’s crucial to understand that this is a short-term measure and does not fully eliminate the risk. A full upgrade should still be prioritized.

References

https://github.com/n8n-io/n8n/security/advisories/GHSA-f77h-j2v7-g6mw

Share
Alex Joseph

Alex Joseph

Alex Joseph is a Senior Support Staff professional with deep experience in server management, web hosting technologies, and cybersecurity operations. He works daily with Linux servers, cloud platforms, performance tuning, and security hardening, giving him strong real-world technical knowledge. Along with his support role, he write about security best practices, hosting infrastructure, and software management.

Related updates

Start Building Today

Ready to Get Started?

VPS, dedicated servers, streaming and managed hosting with 24/7 support from the Ucartz team.