n8n: Edit Image Node Format Injection Allows Arbitrary File Write
## Impact The n8n Edit Image node passed its output format to the underlying image library without validation, so a crafted value could write bytes to a location outside the node's working directory. An authenticated user able to run workflows could use this to write arbitrary files in the n8n instance. ## Patches The issue has been fixed 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. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n instance access to fully trusted users only. - Disable the Edit Image node by adding `n8n-nodes-base.editImage` to the `NODES_EXCLUDE` environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-72762US | high8.8 | — | ||
n8n versions before 1.123.67, 2.31.5, and 2.32.1 contain an arbitrary file write vulnerability in the Edit Image node, which passes its output format parameter to the underlying im… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/n8n-io/n8nPACKAGE
- https://github.com/n8n-io/n8n/commit/f69dfc6dd2178a14ea1624d2e1d403c2e755042fWEB
- https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.67WEB
- https://github.com/n8n-io/n8n/releases/tag/n8n@2.31.5WEB
- https://github.com/n8n-io/n8n/releases/tag/n8n@2.32.1WEB
- https://github.com/n8n-io/n8n/security/advisories/GHSA-xmc9-4f2h-jf9cWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan