{"id":"CVE-2026-54308","title":"n8n: Missing Token Validation on Microsoft Agent 365 Trigger and Stripe Nodes","summary":"n8n: Missing Token Validation on Microsoft Agent 365 Trigger and Stripe Nodes","severity":"medium","cvss":7.2,"cwe":["CWE-290"],"vendor":"n8n","product":"n8n","ecosystem":"npm","affected":["n8n >= 2.26.0, < 2.26.2","n8n < 2.25.7"],"patched":["n8n 2.26.2","n8n 2.25.7"],"published":"2026-06-16","updated":"2026-06-16","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-jvc7-762p-3743","references":[{"url":"https://github.com/n8n-io/n8n/security/advisories/GHSA-jvc7-762p-3743"},{"url":"https://github.com/advisories/GHSA-jvc7-762p-3743"}],"tags":["ghsa","npm"],"epss":0.00299,"epssPercentile":0.20053,"ingestedAt":"2026-06-29T14:31:47.723Z","slug":"CVE-2026-54308","body":"## Overview\n\n## Impact\nThe `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.\n\n## Patches\nThe 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.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Deactivate any workflows using the Microsoft Agent 365 Trigger node or Stripe Trigger node until the instance can be upgraded.\n- Restrict network access to the n8n webhook endpoint to trusted sources only.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.\n\n## Affected packages\n\n- `n8n >= 2.26.0, < 2.26.2`\n- `n8n < 2.25.7`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `n8n 2.26.2`\n- `n8n 2.25.7`","depth":"sunlit","depthScore":40,"depthScoreParts":{"impact":39.6,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}