CVE-2026-110849 n8n-io CVE debrief

Who should care

Roles responsible for managing n8n deployments, user interactions, and security should assess exposure and potential impact. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify affected versions and exposure, and implement necessary mitigations to prevent exploitation.

Why it matters

Defenders should prioritize verifying exposure and assessing potential impact due to the risk of script execution and unauthorized actions in n8n deployments.

• Potential for script execution in the n8n origin
• Possible unauthorized actions with the owner's session
• Risk of compromised user accounts
• Need for verification of affected versions and exposure

Technical summary

The vulnerability exists in the file-preview modal of n8n, where binary data is re-published as an unsandboxed same-origin blob URL. This allows a member who uploads a crafted item to run script in the n8n origin of whoever previews it, typically the owner, and act with their session. The affected product deployments should be verified for exposure, and defenders should assess potential impact due to the risk of script execution and unauthorized actions in n8n deployments. Additional security measures should be implemented to prevent similar vulnerabilities.

Defensive priority

Defenders should prioritize verifying exposure and assessing potential impact, focusing on roles responsible for managing n8n deployments and user interactions.

Recommended defensive actions

• Verify n8n version and assess exposure
• Restrict user uploads and preview permissions
• Implement additional security measures for user interactions
• 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 source item provide details on the vulnerability, including affected versions and a description of the issue. However, additional information on potential exploitation or impact is limited.

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.