CVE-2026-72767
Authenticated RCE in n8n Git node allows execution as n8n process user.
Is CVE-2026-72767 being exploited?
Not confirmed. CVE-2026-72767 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-72767?
CVE-2026-72767 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72767?
Yes. A fix has been recorded for CVE-2026-72767. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72767 affect?
CVE-2026-72767 affects n8n < 1.123.67, n8n 2.x < 2.31.5, n8n 2.32.x < 2.32.1, Self-hosted and cloud n8n instances. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72767?
Upgrade to fixed versions; restrict workflow/repo creation rights; audit and rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users who can create/execute workflows can craft a repo that triggers git hooks to execute arbitrary commands as the n8n process user (remote code execution).
Immediate action required
- affected< 1.123.67
- affected< 2.32.1
- affected< 2.31.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.