CVE-2026-27498: n8n has Arbitrary Command Execution via File Write and Git Operations

Published Feb 25, 2026
·
Updated

Impact An authenticated user with permission to create or modify workflows could chain the Read/Write Files from Disk node with git operations to achieve remote code execution. By writing to specific configuration files and then triggering a git operation, the attacker could execute arbitrary shell commands on the n8n host.

Patches The issue has been fixed in n8n versions 2.2.0 and 1.123.8. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Limit workflow creation and editing permissions to fully trusted users only. - Disable the Read/Write Files from Disk node by adding n8n-nodes-base.readWriteFile to the NODESEXCLUDE environment variable.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Other sources

n8n is an open source workflow automation platform. Prior to versions 2.2.0 and 1.123.8, an authenticated user with permission to create or modify workflows could chain the Read/Write Files from Disk node with git operations to achieve remote code execution. By writing to specific configuration files and then triggering a git operation, the attacker could execute arbitrary shell commands on the n8n host. The issue has been fixed in n8n versions 2.2.0 and 1.123.8. Users should upgrade to one of these versions or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations. Limit workflow creation and editing permissions to fully trusted users only, and/or disable the Read/Write Files from Disk node by adding n8n-nodes-base.readWriteFile to the NODESEXCLUDE environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

NVD

Affected Software

4 affected componentsFixes available
npm/n8n>=2.0.0<2.2.0
2.2.0
npm/n8n<1.123.8
1.123.8
n8n N8n Node.js<1.123.8
n8n N8n Node.js>=2.0.0<2.2.0

Event History

Feb 25, 2026
Advisory Published
via GitHub·09:54 PM
Data Sourced
via GitHub·09:54 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·10:42 PM
Data Sourced
via MITRE·10:42 PM
DescriptionWeakness
Data Sourced
via NVD·11:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:16 PM
RemedyAffected Software
Mar 23, 58145
Event
via FIRST·07:30 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-27498?

CVE-2026-27498 has a high severity due to the potential for arbitrary command execution through user permissions.

2

How do I fix CVE-2026-27498?

To mitigate CVE-2026-27498, upgrade n8n to version 2.2.0 or above, or to version 1.123.8 or below.

3

Who is affected by CVE-2026-27498?

CVE-2026-27498 affects authenticated users of n8n with permissions to create or modify workflows.

4

What are the risks of CVE-2026-27498?

The risks associated with CVE-2026-27498 include the potential for remote code execution, compromising the system.

5

How can I verify if my n8n instance is vulnerable to CVE-2026-27498?

You can verify if your n8n instance is vulnerable to CVE-2026-27498 by checking if it runs between versions 2.0.0 and 2.2.0 or below version 1.123.8.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203