Skip to main content
CVE-2026-21877VulnerabilityPublished

CVE-2026-21877: n8n · Code Injection

Affects n8nSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 10.0 Critical : upgrade to 1.121.3 as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
5.4% chance of exploitation in 30 days – higher than 92% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.121.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jan 2026

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade n8n and n8n-io/n8n to 1.121.3.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • <1.121.3
Fixed in
  • 1.121.3
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <1.121.3
Fixed in
  • 1.121.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade to n8n version 1.121.3 or later, which contains the patch for this vulnerability. 2. Temporarily disable the Git node functionality in n8n to prevent exploitation via this vector. 3. Restrict access to the n8n platform to trusted and authenticated users only, employing strong authentication mechanisms such as MFA. 4. Implement network segmentation to isolate n8n instances from critical infrastructure and sensitive data stores. 5. Monitor logs and network traffic for unusual activity related to n8n, especially attempts to access or manipulate the Git node. 6. Conduct regular security audits and code reviews of custom workflows to detect potential injection points. 7. Educate administrators and users about the risks of code injection and the importance of applying security updates promptly. 8. Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect and block malicious code execution attempts in real time.

Description

n8n is an open source workflow automation platform. In versions 0.121.2 and below, an authenticated attacker may be able to execute malicious code using the n8n service. This could result in full compromise and can impact both self-hosted and n8n Cloud instances. This issue is fixed in version 1.121.3. Administrators can reduce exposure by disabling the Git node and limiting access for untrusted users, but upgrading to the latest version is recommended.

References

Community reviews

Loading reviews…