CVE-2026-110842 n8n-io CVE debrief

Who should care

Defenders responsible for n8n deployments, especially those using workflows, should assess exposure and prioritize verification and potential upgrades. The vulnerability affects n8n versions before 2.41.4 and 2.42.1, allowing an authenticated user with limited permissions to potentially escalate privileges and take over accounts not protected by MFA in n8n deployments using workflows. Verification of exposure and upgrading to fixed versions are crucial for

Why it matters

Defenders should care about CVE-2026-110842 because it allows an authenticated user with limited permissions to potentially escalate privileges and take over accounts not protected by MFA in n8n deployments using workflows. Verification of exposure and upgrading to fixed versions are crucial.

• Potential privilege escalation for authenticated users
• Possible account takeover for users without MFA protection
• Bypass of server-side permission checks
• Verification of workflow configurations and user permissions required

Technical summary

The n8n workflow automation tool contains a prototype pollution vulnerability in its MCP workflow-validation tool. An authenticated user with a workflow:read grant can manipulate the interpreter to replace built-in methods, potentially allowing for privilege escalation and account takeover. The vulnerability affects n8n versions before 2.41.4 and 2.42.1. The tool's interpreter evaluates caller-supplied code in the main process, reads inherited properties, and permits assignment onto shared prototypes. Defenders should prioritize verifying exposure in n8n deployments, especially where workflows are used, and assess the feasibility of upgrading to version 2.41.4 or 2.42.1.

Defensive priority

Defenders should prioritize verifying exposure in n8n deployments, especially where workflows are used, and assess the feasibility of upgrading to version 2.41.4 or 2.42.1.

Recommended defensive actions

• Verify n8n version and assess exposure
• Upgrade to version 2.41.4 or 2.42.1 if possible
• Review workflow configurations and user permissions
• 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.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record and source item provide details on a prototype pollution vulnerability in n8n's MCP workflow-validation tool, which could allow an authenticated user with limited permissions to escalate privileges. The vulnerability affects n8n versions before 2.41.4 and 2.42.1. The tool's interpreter evaluates caller-supplied code in the main process, reads inherited properties, and permits assignment onto shared prototypes. Defenders should verify exposure in n8n deployments, especially where workflows are used, and assess the The

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.