Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalPublic exploit

OS Command Injection in n8n Git node

IdentifiersCVE-2026-25053CWE-78· Improper Neutralization of Special…

CVE-2026-25053 is a critical vulnerability in the n8n workflow automation platform affecting versions prior to 1.123.10 and 2.5.0. The flaw is in the Git node and allows authenticated users with permission to create or modify workflows to execute arbitrary system commands on the host running n8n. The provided content also states the same issue can be abused to read arbitrary files from the n8n host, indicating the Git node breaks isolation between workflow-level functionality and host-level resources. In practice, a user able to edit workflows can abuse Git node functionality to trigger command execution in the underlying operating system context and access sensitive local files.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in full compromise of the n8n host in the security context of the n8n process. An attacker can execute arbitrary OS commands, read sensitive files, access credentials, tokens, configuration data, and other secrets stored on the host, and use that access for follow-on compromise. Given n8n’s typical role orchestrating SaaS, cloud, and internal service credentials, impact can extend to data exfiltration, lateral movement, persistence, and disruption of workflow operations. The advisory rates the issue as CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, limit workflow creation and editing permissions to fully trusted users only, and restrict or disable access to the Git node where it is not operationally required. Deploy n8n in a hardened environment with reduced operating system privileges and constrained network access to limit blast radius. These are temporary risk-reduction measures and not a substitute for upgrading.

Remediation

Patch, then assume compromise.

Upgrade n8n to a fixed version. The issue is patched in n8n 1.123.10 and 2.5.0. Organizations should update to 1.123.10 or later on the 1.x branch, or 2.5.0 or later on the 2.x branch.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
CVE-2026-25053MaturityPoCFrameworkn8n workflow (JSON) using n8n-nodes-base.git and n8n-nodes-base.readWriteFileVerified exploit

Repository is a small PoC labeled CVE-2026-25053 consisting of 4 files: (1) README.md with only the CVE title, (2) .gitattributes setting '* filter=evil' to apply a Git filter to all files, (3) file.txt containing a Git config snippet defining filter "evil" with clean/smudge commands set to "calc.exe" (Windows command execution demo), and (4) workflow.json, an n8n workflow that automates exploitation steps. The n8n workflow structure: Manual Trigger → Git node (clone) clones https://github.com/yadhukrishnam/CVE-2026-25053 into C:\Users\yadhu\.n8n-files\poc → Read/Write node reads a local file (C:\Users\yadhu\.n8n-files\test\file.txt) → Read/Write node appends content into C:\Users\yadhu\.n8n-files\poc\.git\config (injecting the malicious filter definition) → Git node runs 'add' on file.txt. With the attribute forcing the filter and the filter commands defined, subsequent Git operations that invoke clean/smudge can execute the configured command (calc.exe). This is a command-execution PoC rather than a scanner/detector, and it is not a Metasploit/Nuclei module; it is an n8n automation workflow demonstrating a Git-filter-based execution chain.

yadhukrishnamDisclosed Dec 24, 2025jsonmarkdownnetwork (supply-chain style): clone a repository over HTTPS, then trigger local command execution via Git filter processing during subsequent Git operationslocal: writing to .git\\config to inject filter definitions that execute commands
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
N8nN8napplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.