n8n-io n8n up to 1.123.21/2.9.2/2.10.0 uninitialized resource

Summaryinfo

A vulnerability, which was classified as problematic, was found in n8n-io n8n up to 1.123.21/2.9.2/2.10.0. The impacted element is an unknown function. The manipulation results in uninitialized resource. This vulnerability is known as CVE-2026-27496. It is possible to launch the attack remotely. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in n8n-io n8n up to 1.123.21/2.9.2/2.10.0. Affected is some unknown functionality. The manipulation with an unknown input leads to a uninitialized resource vulnerability. CWE is classifying the issue as CWE-908. The product uses or accesses a resource that has not been initialized. This is going to have an impact on confidentiality. CVE summarizes:

n8n is an open source workflow automation platform. Prior to versions 1.123.22, 2.9.3, and 2.10.1, an authenticated user with permission to create or modify workflows could use the JavaScript Task Runner to allocate uninitialized memory buffers. Uninitialized buffers may contain residual data from the same Node.js process — including data from prior requests, tasks, secrets, or tokens — resulting in information disclosure of sensitive in-process data. Task Runners must be enabled using `N8N_RUNNERS_ENABLED=true`. In external runner mode, the impact is limited to data within the external runner process. The issue has been fixed in n8n versions 1.123.22, 2.10.1 , and 2.9.3. Users should upgrade to this version or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only, and/or use external runner mode (`N8N_RUNNERS_MODE=external`) to isolate the runner process. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-27496 since 02/19/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The technical details are unknown and an exploit is not available.

Upgrading to version 1.123.22, 2.9.3 or 2.10.1 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• n8n-io

Name

• n8n

Version

• 1.123.0
• 1.123.1
• 1.123.2
• 1.123.3
• 1.123.4
• 1.123.5
• 1.123.6
• 1.123.7
• 1.123.8
• 1.123.9
• 1.123.10
• 1.123.11
• 1.123.12
• 1.123.13
• 1.123.14
• 1.123.15
• 1.123.16
• 1.123.17
• 1.123.18
• 1.123.19
• 1.123.20
• 1.123.21
• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.9.0
• 2.9.1
• 2.9.2
• 2.10.0

Website

• Product: https://github.com/n8n-io/n8n/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion