CVE-2025-65964: n8n security flaw enables

CISO Take

Any n8n instance running versions 0.123.1–1.119.2 with the Git node enabled is vulnerable to full remote code execution by any user who can create or edit workflows — patch to 1.119.2 immediately. In AI agent environments, n8n often holds API keys for LLMs, databases, and SaaS integrations, making RCE catastrophically impactful beyond just the host. If you cannot patch today, disable the Git node via the node exclusion config and audit recent workflow changes.

What is the risk?

Critical operational risk for AI agent deployments. CVSS 8.8 with network-accessible attack vector, low complexity, and only low-privilege access required means this is exploitable by any workflow editor — including compromised service accounts or insider threats. The absence of user interaction requirement enables fully automated exploitation. n8n is widely deployed as the backbone of AI agent orchestration pipelines, meaning successful exploitation grants access to the full credential store of the automation environment (LLM API keys, database credentials, webhook secrets). Not yet in CISA KEV but exploitation surface is broad.

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
n8n	npm	—	No patch
193.4K OpenSSF 6.6 Pushed 3d ago 55% 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.6%

chance of exploitation in 30 days

Higher than 44% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

Exploit Available

Exploitation: MEDIUM

Sophistication

Moderate

Exploitation Confidence

medium

○ Public PoC indexed (trickest/cve)

Composite signal derived from CISA KEV, VulnCheck KEV, CISA SSVC, EPSS, Metasploit, Exploit-DB, trickest/cve, Nuclei templates, and inthewild.io exploitation reports.

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

PATCH

Upgrade to n8n 1.119.2 immediately — this is the only full fix.
WORKAROUND (if patching is blocked): Exclude the Git node in n8n configuration using nodes.exclude in config/default.json or equivalent environment variable — reference: https://n8n-docs.teamlab.info/hosting/securing/blocking-nodes/#exclude-nodes.
AUDIT

Review recent workflow changes (last 30–90 days) for any workflows using the Git node's Add Config operation, specifically checking for modifications to core.hooksPath.
REVOKE

Rotate all credentials stored in n8n environment variables and workflow credentials store if exploitation cannot be ruled out.
DETECT

Alert on Git processes spawning unusual child processes from the n8n service account; monitor for .git/hooks/ writes or core.hooksPath configuration in Git repos accessible by n8n.
RESTRICT

Limit workflow creation/edit permissions to a minimal set of trusted principals until patching is confirmed.

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 Agent Framework AML.T0049 - Exploit Public-Facing Application AML.T0050 - Command and Scripting Interpreter AML.T0053 - AI Agent Tool Invocation AML.T0072 - Reverse Shell AML.T0081 - Modify AI Agent Configuration AML.T0083 - Credentials from AI Agent Configuration

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act

Article 15 - Accuracy, Robustness and Cybersecurity

ISO 42001

A.6.2.4 - AI System Security A.6.2.6 - Protection of AI system A.8.7 - AI System Operation — Security in Operations

NIST AI RMF

GOVERN 1.7 - Processes for AI Risk Management MANAGE 2.2 - Mechanisms to sustain the treatment of identified AI risks MANAGE 2.4 - Risk Treatment Selection and Prioritization

OWASP LLM Top 10

LLM07 - Insecure Plugin Design LLM08 - Excessive Agency

Frequently Asked Questions

What is CVE-2025-65964?

Any n8n instance running versions 0.123.1–1.119.2 with the Git node enabled is vulnerable to full remote code execution by any user who can create or edit workflows — patch to 1.119.2 immediately. In AI agent environments, n8n often holds API keys for LLMs, databases, and SaaS integrations, making RCE catastrophically impactful beyond just the host. If you cannot patch today, disable the Git node via the node exclusion config and audit recent workflow changes.

Is CVE-2025-65964 actively exploited?

Proof-of-concept exploit code is publicly available for CVE-2025-65964, increasing the risk of exploitation.

How to fix CVE-2025-65964?

1. PATCH: Upgrade to n8n 1.119.2 immediately — this is the only full fix. 2. WORKAROUND (if patching is blocked): Exclude the Git node in n8n configuration using `nodes.exclude` in `config/default.json` or equivalent environment variable — reference: https://n8n-docs.teamlab.info/hosting/securing/blocking-nodes/#exclude-nodes. 3. AUDIT: Review recent workflow changes (last 30–90 days) for any workflows using the Git node's Add Config operation, specifically checking for modifications to `core.hooksPath`. 4. REVOKE: Rotate all credentials stored in n8n environment variables and workflow credentials store if exploitation cannot be ruled out. 5. DETECT: Alert on Git processes spawning unusual child processes from the n8n service account; monitor for `.git/hooks/` writes or `core.hooksPath` configuration in Git repos accessible by n8n. 6. RESTRICT: Limit workflow creation/edit permissions to a minimal set of trusted principals until patching is confirmed.

What systems are affected by CVE-2025-65964?

This vulnerability affects the following AI/ML architecture patterns: AI agent frameworks, workflow automation pipelines, LLM orchestration layers, RAG pipelines, CI/CD pipelines with AI components.

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

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

What is the AI security impact?

Affected AI Architectures

AI agent frameworksworkflow automation pipelinesLLM orchestration layersRAG pipelinesCI/CD pipelines with AI components

MITRE ATLAS Techniques

AML.T0049 Exploit Public-Facing Application

AML.T0050 Command and Scripting Interpreter

AML.T0053 AI Agent Tool Invocation

AML.T0072 Reverse Shell

AML.T0081 Modify AI Agent Configuration

AML.T0083 Credentials from AI Agent Configuration

Compliance Controls Affected

EU AI Act: Article 15

ISO 42001: A.6.2.4, A.6.2.6, A.8.7

NIST AI RMF: GOVERN 1.7, MANAGE 2.2, MANAGE 2.4

OWASP LLM Top 10: LLM07, LLM08

What are the technical details?

Original Advisory

n8n is an open source workflow automation platform. Versions 0.123.1 through 1.119.1 do not have adequate protections to prevent RCE through the project's pre-commit hooks. The Add Config operation allows workflows to set arbitrary Git configuration values, including core.hooksPath, which can point to a malicious Git hook that executes arbitrary commands on the n8n host during subsequent Git operations. Exploitation requires the ability to create or modify an n8n workflow using the Git node. This issue is fixed in version 1.119.2. Workarounds include excluding the Git Node (Docs) and avoiding cloning or interacting with untrusted repositories using the Git Node.

Exploitation Scenario

An adversary with n8n workflow editor access (compromised user account, insider, or via a credential stuffing attack against a publicly exposed n8n instance) creates a new workflow using the Git node. In the workflow, they invoke the 'Add Config' operation to set `core.hooksPath` to a path they control — either a directory in the repository or a writable system path. They populate that directory with a `pre-commit` or `post-checkout` shell script containing a reverse shell or credential exfiltration payload. The workflow then triggers any subsequent Git operation (clone, pull, commit) against any repository. The malicious hook fires with the n8n process privileges, executing arbitrary commands on the host. The attacker extracts n8n's environment variables (LLM API keys, database URLs, Stripe/webhook secrets), pivots into connected AI infrastructure, or deploys a persistent backdoor. The entire chain requires no privileged access — only workflow edit rights.

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.