N8n CVE-2026-33724

The CVSS 6.3 score reflects a medium-severity network-based attack with moderate complexity and partial attack success conditions (AT:P indicates some prerequisite). However, real-world risk is contextually elevated: the vulnerability requires network positioning (MITM capability), which is feasible in cloud environments, shared networks, or compromised ISPs. The attack is not automatable at scale (AC:H, AT:P), limiting opportunistic exploitation. KEV status and POC availability are not explicitly reported in provided intelligence, suggesting limited active weaponization at disclosure time. SSVC framing would classify this as SSVC:1:1:1:1 (exploitation unlikely, automatable=no, technical impact=total, safety impact=minor) due to the explicit configuration requirement and network prerequisites. Organizations with mature network segmentation and non-default feature configurations face lower real-world risk than those exposing n8n instances to untrusted networks.

An attacker positioned on the network path between an n8n instance and its configured Git server (e.g., a compromised ISP router, rogue WiFi access point, or cloud network MITM) intercepts the SSH connection during a workflow sync operation. The attacker presents a fraudulent SSH host key; because host key verification is disabled, the n8n client accepts the connection transparently. The attacker then injects malicious workflow definitions into the source control repository, which are pulled into the n8n instance on the next sync, causing the automation to execute attacker-controlled code with the privileges of the n8n service. Alternatively, the attacker captures credentials or sensitive workflow data transiting the unverified SSH channel.