CVE-2026-72762 n8n-io CVE debrief

Who should care

Defenders and administrators of n8n instances should assess exposure and prioritize remediation due to the high severity of this vulnerability. They should verify affected instances, restrict user access to workflow execution, and apply vendor patches. Additionally, they should review compensating controls, monitor workflow execution, and track exceptions to ensure the vulnerability is properly addressed.

Why it matters

CVE-2026-72762 is a high-severity vulnerability in n8n that allows authenticated users to write arbitrary files outside the node's working directory. Defenders should prioritize verifying affected instances, restricting user access, and applying patches.

• Potential unauthorized file writes outside the node's working directory
• Possible data integrity and confidentiality impacts
• Required verification of affected n8n instances and user access controls
• Necessary application of vendor patches or updates

Technical summary

The Edit Image node in n8n versions before 1.123.67, 2.31.5, and 2.32.1 contains an arbitrary file write vulnerability. An authenticated user able to run workflows can supply a crafted format value to write arbitrary files outside the node's working directory on the n8n instance. This vulnerability has a high CVSS score of 7.7 and is classified as HIGH severity. The vulnerability impacts n8n instances, allowing attackers to write files outside the node's working directory, potentially leading to data integrity and confidentiality impacts.

Defensive priority

Defenders should prioritize verifying affected n8n instances, restricting user access to workflow execution, and applying vendor patches.

Recommended defensive actions

• Verify n8n instance versions and restrict user access to workflow execution
• Apply patches or updates to affected n8n versions
• Monitor workflow execution and node usage for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but vendor confirmation and additional sources are limited. Defenders should verify affected n8n instances, restrict user access to workflow execution, and apply vendor patches. The vulnerability's high severity and potential impact on data integrity and confidentiality necessitate prompt attention. Limited source details are available, so defenders must exercise caution and verify information through multiple channels.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.