CVE-2025-62726: n8n security flaw enables

CISO Take

Any n8n instance below 1.113.0 is a credential dump waiting to happen. An attacker with a low-privilege n8n account can host a malicious git repo with a poisoned pre-commit hook, trigger RCE the moment any workflow runs a Commit operation, and walk away with every API key, OAuth token, and database password stored in your automation platform. Patch to 1.113.0 immediately — if you cannot, rotate all n8n-stored credentials now and disable Git Node access.

What is the risk?

HIGH risk in practice, warranting treatment as critical in AI automation environments. CVSS 8.8 with network-accessible, low-complexity, low-privilege exploitation and no meaningful user interaction barrier. The blast radius is disproportionate to the severity score: n8n environments aggregate credentials for every integrated service (cloud APIs, databases, SaaS tools, LLM providers). Organizations running n8n as an AI orchestration backbone should escalate to critical given the credential and lateral-movement exposure.

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
n8n	npm	—	No patch
193.4K OpenSSF 6.6 Pushed 3d ago 54% patched ~7d to patch Full package profile →

Do you use n8n? You're affected.

How severe is it?

CVSS 3.1

8.8 / 10

EPSS

0.7%

chance of exploitation in 30 days

Higher than 49% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

No known exploitation

Sophistication

Trivial

What is the attack surface?

AV Network

AC Low

PR Low

UI None

S Unchanged

C High

I High

A High

What should I do?

6 steps

IMMEDIATE

Upgrade n8n to 1.113.0 or later — the only complete fix.
DETECT

Audit all workflows for Git Node usage; flag any that clone external or user-supplied repositories.
RESTRICT

Treat Git Node access as a privileged operation — limit who can create or modify workflows containing Git Nodes.
ROTATE

If patching is delayed, proactively rotate all credentials stored in n8n (API keys, OAuth tokens, DB passwords).
ISOLATE

Ensure n8n runs in a container with minimal host permissions, network egress restrictions, and no direct mount of sensitive host paths.
MONITOR

Alert on unexpected outbound connections and process spawning from the n8n process — a reverse shell will be the typical payload.

What does CISA's SSVC say?

Decision Track

Exploitation none

Automatable No

Technical Impact total

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Code Execution Supply Chain Data Extraction Agent Framework Plugin AML.T0010.001 - AI Software AML.T0049 - Exploit Public-Facing Application AML.T0050 - Command and Scripting Interpreter AML.T0053 - AI Agent Tool Invocation AML.T0072 - Reverse Shell AML.T0083 - Credentials from AI Agent Configuration

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act

Art. 15 - Accuracy, robustness and cybersecurity

ISO 42001

A.6.2.3 - AI supply chain security A.7.4 - Protection of AI systems

NIST AI RMF

MANAGE 2.2 - Mechanisms to sustain AI risk management

OWASP LLM Top 10

LLM08 - Excessive Agency

Frequently Asked Questions

What is CVE-2025-62726?

Any n8n instance below 1.113.0 is a credential dump waiting to happen. An attacker with a low-privilege n8n account can host a malicious git repo with a poisoned pre-commit hook, trigger RCE the moment any workflow runs a Commit operation, and walk away with every API key, OAuth token, and database password stored in your automation platform. Patch to 1.113.0 immediately — if you cannot, rotate all n8n-stored credentials now and disable Git Node access.

Is CVE-2025-62726 actively exploited?

No confirmed active exploitation of CVE-2025-62726 has been reported, but organizations should still patch proactively.

How to fix CVE-2025-62726?

1. IMMEDIATE: Upgrade n8n to 1.113.0 or later — the only complete fix. 2. DETECT: Audit all workflows for Git Node usage; flag any that clone external or user-supplied repositories. 3. RESTRICT: Treat Git Node access as a privileged operation — limit who can create or modify workflows containing Git Nodes. 4. ROTATE: If patching is delayed, proactively rotate all credentials stored in n8n (API keys, OAuth tokens, DB passwords). 5. ISOLATE: Ensure n8n runs in a container with minimal host permissions, network egress restrictions, and no direct mount of sensitive host paths. 6. MONITOR: Alert on unexpected outbound connections and process spawning from the n8n process — a reverse shell will be the typical payload.

What systems are affected by CVE-2025-62726?

This vulnerability affects the following AI/ML architecture patterns: AI agent orchestration platforms, workflow automation pipelines, agent frameworks, LLM tool-use integrations, CI/CD automation with AI integration.

What is the CVSS score for CVE-2025-62726?

CVE-2025-62726 has a CVSS v3.1 base score of 8.8 (HIGH). The EPSS exploitation probability is 0.73%.

What is the AI security impact?

Affected AI Architectures

AI agent orchestration platformsworkflow automation pipelinesagent frameworksLLM tool-use integrationsCI/CD automation with AI integration

MITRE ATLAS Techniques

AML.T0010.001 AI Software

AML.T0049 Exploit Public-Facing Application

AML.T0050 Command and Scripting Interpreter

AML.T0053 AI Agent Tool Invocation

AML.T0072 Reverse Shell

AML.T0083 Credentials from AI Agent Configuration

Compliance Controls Affected

EU AI Act: Art. 15

ISO 42001: A.6.2.3, A.7.4

NIST AI RMF: MANAGE 2.2

OWASP LLM Top 10: LLM08

What are the technical details?

Original Advisory

n8n is an open source workflow automation platform. Prior to 1.113.0, a remote code execution vulnerability exists in the Git Node component available in both Cloud and Self-Hosted versions of n8n. When a malicious actor clones a remote repository containing a pre-commit hook, the subsequent use of the Commit operation in the Git Node can inadvertently trigger the hook’s execution. This allows attackers to execute arbitrary code within the n8n environment, potentially compromising the system and any connected credentials or workflows. This vulnerability is fixed in 1.113.0.

Exploitation Scenario

Attacker registers a low-privilege account on a shared n8n instance (or compromises one via credential stuffing). They create a workflow that clones a GitHub repository they control — the repo contains a .git/hooks/pre-commit script with a reverse shell payload. The workflow is saved and triggered on a schedule or by a webhook. When n8n's Git Node executes the Commit operation against the cloned repository, the pre-commit hook fires inside n8n's runtime. The attacker receives a reverse shell, dumps n8n's encrypted credential store, and pivots to every API, database, and cloud service the automation platform touches — including any connected LLM providers, vector databases, or internal AI tools.

Weaknesses (CWE)

CWE-829 Inclusion of Functionality from Untrusted Control Sphere

CWE-829 — Inclusion of Functionality from Untrusted Control Sphere: The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.

[Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
[Architecture and Design] When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs. For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap [REF-45] provide this capability.

Source: MITRE CWE corpus.