CVE-2026-54308: n8n: Missing Token Validation on Microsoft Agent 365 Trigger Node
Impact The MicrosoftAgent365Trigger and StripeTrigger node did not validate that inbound requests. As a result, an unauthenticated attacker who knows the webhook URL could submit a forged payload and cause the workflow to execute with attacker-controlled data.
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: - Deactivate any workflows using the Microsoft Agent 365 Trigger node or Stripe Trigger node until the instance can be upgraded. - Restrict network access to the n8n webhook endpoint to trusted sources 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, the MicrosoftAgent365Trigger and StripeTrigger node did not validate that inbound requests. As a result, an unauthenticated attacker who knows the webhook URL could submit a forged payload and cause the workflow to execute with attacker-controlled data. 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
n8nto a version that resolves this vulnerability.Fixed in 2.25.7 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.26.2 - Configuration
Deactive any workflows that use the Microsoft Agent 365 Trigger node or the Stripe Trigger node until the n8n instance can be upgraded.
n8n workflows Disable workflows using trigger nodes = Deactivate workflows using Microsoft Agent 365 Trigger node or Stripe Trigger node - Compensating control
Restrict network access to the n8n webhook endpoint to trusted sources only.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-54308?
The severity of CVE-2026-54308 is rated high with a CVSS score of 7.2.
What impact does CVE-2026-54308 have on my application?
CVE-2026-54308 allows unauthenticated attackers to exploit the workflow with forged payloads, potentially leading to execution of malicious actions.
How do I fix CVE-2026-54308?
To fix CVE-2026-54308, ensure that incoming requests to the MicrosoftAgent365Trigger and StripeTrigger nodes are properly validated.
Who is affected by CVE-2026-54308?
CVE-2026-54308 affects users of the npm/n8n application utilizing the MicrosoftAgent365Trigger and StripeTrigger nodes.
What version of n8n addresses CVE-2026-54308?
Check the latest security advisories for n8n to find versions of the application that contain patches for CVE-2026-54308.