CVE-2026-44789
Awaiting Analysis Awaiting Analysis - Queue
Prototype Pollution in n8n Workflow Automation

Publication date: 2026-06-23

Last updated on: 2026-06-23

Assigner: GitHub, Inc.

Description
n8n is an open source workflow automation platform. Prior to 1.123.43, 2.22.1, and 2.20.7, an authenticated user with permission to create or modify workflows could achieve global prototype pollution via an unvalidated pagination parameter in the HTTP Request node. Combined with other techniques this could lead to RCE on the instance. This vulnerability is fixed in 1.123.43, 2.22.1, and 2.20.7.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-23
Last Modified
2026-06-23
Generated
2026-06-23
AI Q&A
2026-06-23
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
n8n n8n to 1.123.43 (exc)
n8n n8n to 2.20.7 (exc)
n8n n8n to 2.22.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1321 The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

The provided information does not specify how this vulnerability directly affects compliance with common standards and regulations such as GDPR or HIPAA.

Mitigation Strategies

To mitigate the vulnerability in n8n prior to versions 1.123.43, 2.20.7, and 2.22.1, you should upgrade to one of these patched versions or later.

As temporary mitigations, you can restrict workflow creation permissions to trusted users only or disable the HTTP Request node by using the NODES_EXCLUDE environment variable.

Executive Summary

CVE-2026-44789 is a critical vulnerability in n8n, an open-source workflow automation platform. It affects versions prior to 1.123.43, 2.20.7, and 2.22.1. The vulnerability arises from an unvalidated pagination parameter in the HTTP Request node, which allows an authenticated user with permission to create or modify workflows to perform global prototype pollution.

Prototype pollution is a type of security flaw where an attacker can modify the prototype of a base object, potentially altering the behavior of the application globally.

When combined with other techniques, this vulnerability can lead to remote code execution (RCE) on the affected n8n instance, allowing an attacker to execute arbitrary code.

The issue is classified as CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes).

Impact Analysis

This vulnerability can have severe impacts if exploited. An attacker who is authenticated and has permission to create or modify workflows can exploit the prototype pollution flaw to achieve remote code execution (RCE) on the n8n instance.

Remote code execution allows the attacker to run arbitrary code on the server hosting n8n, potentially leading to full system compromise, data theft, data manipulation, or disruption of services.

Because the vulnerability requires workflow modification permissions, the risk can be mitigated by restricting these permissions to trusted users only.

Detection Guidance

This vulnerability affects n8n versions prior to 1.123.43, 2.20.7, and 2.22.1 and involves prototype pollution via an unvalidated pagination parameter in the HTTP Request node. Detection involves verifying the version of n8n running on your system and checking if the HTTP Request node is used with pagination parameters by authenticated users with workflow modification permissions.

To detect if your system is vulnerable, first identify the n8n version by running a command on the server hosting n8n, such as:

  • Check the n8n version via CLI or Docker: `n8n --version` or `docker exec <container_name> n8n --version`
  • Review workflow configurations for usage of the HTTP Request node with pagination parameters, which may require inspecting workflow JSON files or using the n8n API.

Since the vulnerability requires authenticated users with workflow modification permissions, auditing user permissions and workflow creation/modification logs can help detect potential exploitation attempts.

No specific network commands or signatures are provided in the available resources to detect exploitation attempts directly on the network.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44789. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart