CVE-2025-65964: 
NixOS vulnerability analysis and mitigation

CVE-2025-65964 is a Remote Code Execution (RCE) vulnerability in the n8n workflow automation platform's Git node, enabling arbitrary command execution on the underlying host via malicious Git hook configuration. It affects n8n versions ≥ 0.123.1 and < 1.119.2 (npm package). The vulnerability was published on December 8, 2025, by researcher Malayke, and patched in version 1.119.2 released November 14, 2025. It carries a CVSS v3.1 score of 8.8 (High) and a CVSS v4.0 score of 9.4 (Critical) (Github Advisory, n8n Security Advisory).

The root cause is classified as CWE-829 (Inclusion of Functionality from Untrusted Control Sphere). The n8n Git node's "Add Config" operation allows workflows to set arbitrary Git configuration values without restriction. An attacker can set the core.hooksPath Git configuration option to point to a directory within a cloned repository that contains a malicious script (e.g., a pre-commit hook). When a subsequent Git operation is triggered, Git automatically executes the hook as a local system command, resulting in arbitrary code execution under the n8n process's privileges. Exploitation requires low-level privileges — specifically, the ability to create or modify an n8n workflow that uses the Git node — and no user interaction is needed (n8n Security Advisory, Patch Commit).

Successful exploitation grants an attacker arbitrary command execution on the n8n host system with the privileges of the n8n process, resulting in full compromise of confidentiality, integrity, and availability. An attacker could exfiltrate sensitive workflow data, credentials stored in n8n, and environment variables; modify or destroy workflows and data; or use the compromised host as a pivot point for lateral movement within the network. The CVSS v4.0 scoring also reflects high impact on subsequent systems, underscoring the risk to connected infrastructure (n8n Security Advisory, Github Advisory).

Multiple public proof-of-concept repositories have been published, including CVE-2025-65964-poc, n8n-CVE-2025-65964, Blackash-CVE-2025-65964, and CVE-2025-65964-POC. The Belgium Centre for Cybersecurity (CCB) issued a warning urging immediate patching. The EPSS score is approximately 0.033–0.042%, indicating a currently low but non-negligible probability of exploitation in the wild. There is no confirmed attribution to specific threat actors, and the vulnerability is not currently listed in the CISA KEV catalog. Broader abuse of n8n webhooks for malware and phishing campaigns has been observed, highlighting the platform's attractiveness as an attack surface (Github Advisory, Rescana Report).

1. Reconnaissance: Identify internet-facing or internally accessible n8n instances running versions ≥ 0.123.1 and < 1.119.2. Use tools like Shodan or Censys to find exposed n8n deployments (default port 5678).
2. Obtain workflow access: Acquire credentials or a low-privilege account with permission to create or modify n8n workflows. This could be via credential theft, phishing, or abuse of shared/multi-tenant n8n environments.
3. Create or modify a workflow with the Git node: In the n8n workflow editor, add a Git node and configure it to use the "Add Config" operation. Set the configuration key to core.hooksPath and the value to a directory path within the target repository that the attacker controls (e.g., .git/hooks or a custom subdirectory).
4. Plant the malicious hook: Ensure the target repository (cloned or attacker-controlled) contains an executable script at the specified hooks path named pre-commit (or another relevant hook). This script contains the attacker's payload (e.g., a reverse shell command or data exfiltration command).
5. Trigger Git operation: Execute the workflow, causing the Git node to perform a Git operation (e.g., commit, clone) on the repository. Git reads the core.hooksPath configuration and executes the malicious hook script as a local system command on the n8n host.
6. Achieve code execution: The hook script runs with the privileges of the n8n process, enabling reverse shell establishment, credential harvesting, or further lateral movement (n8n Security Advisory, Patch Commit).

• Network: Unexpected outbound connections from the n8n host to unknown external IPs or domains, particularly following Git node workflow executions; reverse shell traffic on non-standard ports originating from the n8n process.
• File System: Presence of executable scripts in Git hook directories (e.g., pre-commit, post-commit) within repositories cloned by n8n; new or modified files in the n8n working directory created by the n8n process unexpectedly.
• Logs: n8n workflow execution logs showing Git node "Add Config" operations setting core.hooksPath to unusual paths; system logs (e.g., /var/log/syslog, auditd) recording unexpected child process spawning from the n8n Node.js process.
• Process: Unusual child processes spawned by the n8n Node.js process (e.g., /bin/bash, sh, curl, wget, python, nc) following Git node workflow execution; unexpected cron jobs or scheduled tasks created under the n8n service account.

The primary remediation is to upgrade n8n to version 1.119.2 or later, which disables Git hooks by default by setting core.hooksPath=/dev/null in all Git node operations (n8n Release, Patch Commit). If upgrading is not immediately possible, administrators should exclude the Git node from allowed nodes using n8n's node blocking feature, and avoid cloning or interacting with untrusted repositories via the Git node. Additionally, restrict workflow creation and modification permissions to trusted users, implement strict access controls on n8n instances, review all existing workflows for suspicious Git node configurations, and use network segmentation to limit the blast radius of a potential compromise (Github Advisory). For environments that legitimately require Git hooks, the new N8N_GIT_NODE_ENABLE_HOOKS=true environment variable can re-enable this functionality after upgrading.

The Belgium Centre for Cybersecurity (CCB) issued a public warning urging organizations to patch immediately, highlighting the critical severity of the RCE risk. Security researchers published multiple PoC repositories within days of disclosure, and the vulnerability was featured in Reddit's CVEWatch "Top 10 Trending CVEs" lists for multiple weeks in December 2025. Security outlets including SecurityOnline.info and Penligent.ai published technical write-ups, with Penligent noting the particular risk to AI infrastructure given n8n's growing use in AI workflow automation. Rescana published a broader threat intelligence report on the abuse of n8n webhooks for malware and phishing campaigns, contextualizing this CVE within a wider pattern of n8n platform targeting (Rescana Report, SecurityOnline).