n8n: Edit Image Node Format Injection Allows Arbitrary File Write
The n8n Edit Image node had a vulnerability where it passed the output format to the image library without validation, allowing an authenticated user running workflows to write arbitrary files outside the node's working directory. This could lead to arbitrary file writes on the n8n instance. The issue is fixed in versions 1.123.67, 2.31.5, and 2.32.1. Temporary mitigations include restricting access to trusted users and disabling the Edit Image node via environment configuration.
AI Analysis
Technical Summary
The n8n Edit Image node improperly handled the output format parameter by not validating it before passing it to the underlying image processing library. This flaw allowed an authenticated user with workflow execution permissions to craft a value that causes arbitrary file writes outside the intended directory, potentially compromising the n8n instance's file system integrity. The vulnerability is tracked under CWE-73 (External Control of File Name or Path). It has been remediated in n8n versions 1.123.67, 2.31.5, and 2.32.1. Until upgrading, administrators can restrict access or disable the vulnerable node as a temporary mitigation.
Potential Impact
An authenticated user able to run workflows can exploit this vulnerability to write arbitrary files anywhere on the n8n instance's file system outside the node's working directory. This could lead to unauthorized file modification or code execution depending on the files written and the environment. The vulnerability does not affect unauthenticated users and requires workflow execution privileges.
Mitigation Recommendations
A fix is available in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability. If immediate upgrade is not possible, restrict n8n instance access to fully trusted users only and disable the Edit Image node by adding 'n8n-nodes-base.editImage' to the NODES_EXCLUDE environment variable. These workarounds reduce risk but do not fully remediate the vulnerability.
n8n: Edit Image Node Format Injection Allows Arbitrary File Write
Description
The n8n Edit Image node had a vulnerability where it passed the output format to the image library without validation, allowing an authenticated user running workflows to write arbitrary files outside the node's working directory. This could lead to arbitrary file writes on the n8n instance. The issue is fixed in versions 1.123.67, 2.31.5, and 2.32.1. Temporary mitigations include restricting access to trusted users and disabling the Edit Image node via environment configuration.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The n8n Edit Image node improperly handled the output format parameter by not validating it before passing it to the underlying image processing library. This flaw allowed an authenticated user with workflow execution permissions to craft a value that causes arbitrary file writes outside the intended directory, potentially compromising the n8n instance's file system integrity. The vulnerability is tracked under CWE-73 (External Control of File Name or Path). It has been remediated in n8n versions 1.123.67, 2.31.5, and 2.32.1. Until upgrading, administrators can restrict access or disable the vulnerable node as a temporary mitigation.
Potential Impact
An authenticated user able to run workflows can exploit this vulnerability to write arbitrary files anywhere on the n8n instance's file system outside the node's working directory. This could lead to unauthorized file modification or code execution depending on the files written and the environment. The vulnerability does not affect unauthenticated users and requires workflow execution privileges.
Mitigation Recommendations
A fix is available in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability. If immediate upgrade is not possible, restrict n8n instance access to fully trusted users only and disable the Edit Image node by adding 'n8n-nodes-base.editImage' to the NODES_EXCLUDE environment variable. These workarounds reduce risk but do not fully remediate the vulnerability.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-xmc9-4f2h-jf9c
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a6150cc9c2644c7f8da0132
Added to database: 07/22/2026, 23:22:52 UTC
Last enriched: 07/22/2026, 23:27:01 UTC
Last updated: 07/22/2026, 23:27:01 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.