AI agent vulnerability · n8n

CVE-2026-54308: n8n: Missing Token Validation on Microsoft Agent 365 Trigger and Stripe Nodes

mediumCVSS 4.0 6.3 · 3.1 7.2GHSA-jvc7-762p-3743

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.

Published Jun 16, 2026 · Updated Jul 20, 2026

Affected packages

n8n

Ecosystem: npm
Affected: >= 2.26.0, < 2.26.2
Fixed in: 2.26.2
Check: npm ls n8n

n8n

Ecosystem: npm
Affected: < 2.25.7
Fixed in: 2.25.7
Check: npm ls n8n

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to nkoorty, jjjutla.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More n8n vulnerabilities

All n8n entries