Ad · Leaderboard 728×90

CVE-2026-110853

7.1High

Published 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

7.1High
Attack vector
Network
Complexity
Low
Privileges needed
Low
User interaction
None
Impact
High impact on confidentiality
Weakness
CWE-639

Impact

Authenticated members can access credentials from projects they do not belong to and tamper with other workflows' static data and error handling. Attackers need a valid low-privileged account with network access to the n8n instance.

Root cause

The Execute Sub-workflow node does not validate workflow identity when supplied with arbitrary trusted identifiers in inline JSON mode.

Affected systems

n8n versions prior to 1.123.83

CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Fix & remediation

Upgrade n8n to version 1.123.83 or later. No interim mitigation is documented, so restrict workflow creation permissions to trusted users until upgraded.

shell
$ npm install -g n8n@1.123.83

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

n8n before 1.123.83 contains an authorization bypass vulnerability that allows authenticated members to spoof workflow identity by supplying a trusted identifier in Execute Sub-workflow inline JSON mode. Attackers can set this identifier to resolve credentials from projects they do not belong to and modify another workflow's static data and error-workflow dispatch.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-110853

Ad · Sticky 320×50 / 728×90