CVE-2026-54306: n8n: Prototype Pollution enables confused-deputy execution via public webhooks
Impact A prototype pollution vulnerability allowed a crafted public webhook payload to inject attacker-controlled fields into workflow data during internal object copying. These fields could be surfaced and consumed as normal values by downstream built-in nodes.
Where a workflow combines a public webhook with action nodes that consume the resulting fields, an attacker could cause the workflow to act as a confused deputy — targeting unintended records or issuing outbound requests using the workflow owner's configured credentials.
Patches The issue has been fixed in n8n versions 2.25.7, and 2.26.2. 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: - Avoid exposing public (unauthenticated) webhook workflows that pass incoming data through transform nodes into action nodes with sensitive credentials or database operations. - Limit workflow creation and editing permissions to fully trusted users only.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Other sources
n8n is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, a prototype pollution vulnerability allowed a crafted public webhook payload to inject attacker-controlled fields into workflow data during internal object copying. These fields could be surfaced and consumed as normal values by downstream built-in nodes. Where a workflow combines a public webhook with action nodes that consume the resulting fields, an attacker could cause the workflow to act as a confused deputy — targeting unintended records or issuing outbound requests using the workflow owner's configured credentials. This vulnerability is fixed in 2.25.7 and 2.26.2.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.25.7 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.26.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.25.7 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.26.2 - Compensating control
Avoid exposing public (unauthenticated) webhook workflows that pass incoming data through transform nodes into action nodes with sensitive credentials or database operations.
- Compensating control
Limit workflow creation and editing permissions to fully trusted users only.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-54306?
The severity of CVE-2026-54306 is medium with a score of 5.4.
How does the CVE-2026-54306 vulnerability occur?
CVE-2026-54306 occurs due to prototype pollution from a crafted public webhook payload that injects attacker-controlled fields into workflow data.
What systems are affected by CVE-2026-54306?
CVE-2026-54306 affects the npm package n8n.
What is the potential impact of CVE-2026-54306?
The potential impact of CVE-2026-54306 includes attackers being able to manipulate workflow data, potentially compromising downstream nodes.
How do I fix CVE-2026-54306?
To fix CVE-2026-54306, update to the latest patched version of the n8n software.