NewApp Monitoring is liveSign up free
AgentbeamBeta
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

n8n's Microsoft Agent 365 Trigger and Stripe Trigger nodes did not validate inbound requests. Anyone who knows the webhook URL can post a forged payload and make the workflow run with attacker-controlled data. Fixed in n8n 2.25.7 and 2.26.2.

Published Jun 16, 2026 · Updated Jul 20, 2026 · Analysis Nov 2, 2026

What an attacker can do

A trigger webhook should check that a request really comes from Microsoft or Stripe, for example through a token or signature. These two nodes skipped that check. The webhook accepted any request that reached its URL, and the workflow then processed the body as if the real service had sent it.

The attacker needs no account and no user interaction. They need only the webhook URL, which the advisory lists as an attack requirement. URLs can leak through logs, shared configuration, screenshots or the partner dashboards that store them.

What the attacker gets depends on the workflow. A forged Stripe event can look like a payment, refund or subscription change, and the workflow may fulfil an order, grant access or write to a database. A forged Agent 365 message feeds attacker text into whatever follows the trigger, including AI agent steps. The advisory rates confidentiality and integrity impact as low, with no availability impact, and marks scope as changed in the 3.1 vector.

Who is affected

n8n on npm below 2.25.7, and versions 2.26.0 and 2.26.1. Only workflows that use the Microsoft Agent 365 Trigger or the Stripe Trigger node are exposed. Check your version:

npm ls n8n

Then look for active workflows that contain either trigger node.

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

How to fix it

Upgrade to n8n 2.25.7 or 2.26.2, or later.

npm install -g [email protected]

If you cannot upgrade yet, the advisory suggests two temporary steps that it says do not fully remove the risk. Deactivate workflows that use the Microsoft Agent 365 Trigger or Stripe Trigger node. Or restrict network access to the n8n webhook endpoint to trusted sources only.

How to tell if you were hit

The advisory lists no indicators. Review execution history for workflows using these two triggers. Look for runs whose payloads do not match real Stripe events or Agent 365 messages, or runs at times with no matching activity in the Stripe dashboard or Microsoft tenant. Check webhook access logs for source IPs that do not belong to Stripe or Microsoft. Check any downstream records the workflow created or changed, such as orders, credits or account flags.

Original advisory

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.

Questions

Is the Stripe Trigger node in n8n affected by CVE-2026-54308?

Yes, along with the Microsoft Agent 365 Trigger. Both failed to validate inbound requests. Upgrade to 2.25.7 or 2.26.2 or later.

Does the attacker need credentials for CVE-2026-54308?

No credentials. They need to know the webhook URL, and then they can send a forged payload with no authentication.

Can I mitigate CVE-2026-54308 without upgrading?

Partly. Deactivate workflows using these triggers, or limit network access to the webhook endpoint to trusted sources. The advisory says neither fully fixes the problem.

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. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More n8n vulnerabilities

All n8n entries