Authenticated command execution via writable Git configuration
Published Feb 25, 2026 · Updated Feb 25, 2026
Code injection in affected n8n releases allows remote authenticated users with workflow-editing rights to execute host commands. The Read/Write Files from Disk node accepted paths inside .git directories, allowing a crafted workflow to overwrite Git configuration before a Git operation triggers shell-command execution. Successful exploitation requires permission to create or modify workflows and runs arbitrary commands with the privileges of the n8n service.
Summary
What happened
Code injection in affected n8n releases allows remote authenticated users with workflow-editing rights to execute host commands. The Read/Write Files from Disk node accepted paths inside .git directories, allowing a crafted workflow to overwrite Git configuration before a Git operation triggers shell-command execution. Successful exploitation requires permission to create or modify workflows and runs arbitrary commands with the privileges of the n8n service.
The record
- CVE
- CVE-2026-27498
- Published
- Feb 25, 2026
- Updated
- Feb 25, 2026
- Vendor
- n8n
- Product
- n8n
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 25, 2026CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.123.8
- Affected versionversion=>= 2.0.0, < 2.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo