CVE-2026-25053

9.9 CRITICAL

📋 TL;DR

This vulnerability in n8n workflow automation platform allows authenticated users with workflow creation/modification permissions to execute arbitrary system commands or read arbitrary files on the host. It affects all n8n installations prior to versions 1.123.10 and 2.5.0. The issue stems from improper input validation in the Git node functionality.

💻 Affected Systems

Products:
  • n8n
Versions: All versions prior to 1.123.10 and 2.5.0
Operating Systems: All platforms running n8n
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated user with permission to create or modify workflows. The Git node must be available/accessible in the workflow editor.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise allowing attackers to execute arbitrary commands with the privileges of the n8n process, potentially leading to complete host takeover, data exfiltration, or lateral movement.

🟠

Likely Case

Authenticated attackers with workflow permissions can execute limited commands or read sensitive files, potentially escalating privileges or accessing confidential data.

🟢

If Mitigated

With proper access controls limiting workflow creation/modification to trusted users only, impact is reduced to authorized users who could still abuse their legitimate access.

🌐 Internet-Facing: HIGH if n8n is exposed to the internet and has authenticated users with workflow permissions, as attackers could gain initial access through credential theft or other means.
🏢 Internal Only: MEDIUM as it requires authenticated access with specific permissions, but insider threats or compromised accounts could exploit it.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access but appears straightforward once authenticated with appropriate permissions. The advisory suggests the vulnerability is in how Git node parameters are handled.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.123.10 or 2.5.0

Vendor Advisory: https://github.com/n8n-io/n8n/security/advisories/GHSA-9g95-qf3f-ggrw

Restart Required: Yes

Instructions:

1. Stop n8n service. 2. Update n8n to version 1.123.10 (if using n8n 1.x) or 2.5.0 (if using n8n 2.x). 3. Restart n8n service. 4. Verify the update was successful.

🔧 Temporary Workarounds

Disable Git node

all

Remove or disable the Git node functionality to prevent exploitation

Modify n8n configuration to disable Git node or remove it from available nodes

Restrict workflow permissions

all

Limit which users can create or modify workflows to only trusted administrators

Configure n8n user roles to restrict workflow creation/modification permissions

🧯 If You Can't Patch

  • Implement strict access controls to limit workflow creation/modification to minimal trusted users
  • Monitor for suspicious workflow modifications or Git node usage in audit logs

🔍 How to Verify

Check if Vulnerable:

Check n8n version: if running version below 1.123.10 (for n8n 1.x) or below 2.5.0 (for n8n 2.x), the system is vulnerable.

Check Version:

n8n --version or check package.json version in n8n installation directory

Verify Fix Applied:

After updating, verify the version is 1.123.10 or higher (for 1.x) or 2.5.0 or higher (for 2.x). Test that Git node functionality still works but with proper input validation.

📡 Detection & Monitoring

Log Indicators:

  • Unusual Git node usage patterns
  • Workflow modifications by non-admin users
  • Commands executed via workflow that appear suspicious

Network Indicators:

  • Unexpected outbound connections from n8n host
  • Git operations to unusual repositories

SIEM Query:

source="n8n" AND (event="workflow_modified" OR event="node_executed") AND node_type="git"

🔗 References

📤 Share & Export