Skip to main content
VulnerabilityPublished Updated

CVE-2026-72767: n8n · OS Command Injection

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 1.123.67 soon.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
EPSS
0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.123.67, 2.32.1, 2.31.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

  5. 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 9 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • <1.123.67
Fixed in
  • 1.123.67
n8n-ion8nAffected
  • >=2.32.0 <2.32.1
Fixed in
  • 2.32.1
n8n-ion8nAffected
  • >=2.0.0-rc.0 <2.31.5
Fixed in
  • 2.31.5
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <1.123.67
  • <2.31.5
  • <2.32.1
Fixed in
  • 1.123.67
  • 2.31.5
  • 2.32.1
npmn8npkg:npm/n8nOther threatsAffected
  • <1.123.67
  • >=2.32.0 <2.32.1
  • >=2.0.0-rc.0 <2.31.5
Fixed in
  • 1.123.67
  • 2.32.1
  • 2.31.5

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

AI-suggested

If you cannot patch yet, restrict workflow creation and execution permissions to trusted users only. Monitor for unusual git hook activity and consider disabling or sandboxing git hooks if possible.

Description

n8n before 1.123.67, 2.x before 2.31.5, and 2.32.x before 2.32.1 contain a remote code execution vulnerability in the Git node. Authenticated users with rights to create and execute workflows can stage a crafted local repository that causes git to run hooks under default git security settings, executing arbitrary commands as the n8n process user. Both self-hosted and cloud instances are affected.

References

Community reviews

Loading reviews…