GHSA-jvc7-762p-3743 CVE-2026-54308

n8n: Missing Token Validation on Microsoft Agent 365 Trigger and Stripe Nodes

High npm

Severity: 0.0 / 10; High · CVSS 4.0
Exploit chance (EPSS): 0.30%; Chance of exploitation in the next 30 days. Higher than 22.62% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-290 Authentication Bypass by Spoofing
Fix: 2.26.2; Upgrade n8n to this version or later

Description

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.

Affected versions

npm

Package	Vulnerable	Fixed in
n8n	`>= 2.26.0, < 2.26.2`	`2.26.2`
n8n	`< 2.25.7`	`2.25.7`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

n8n npm → `2.26.2`

npm

npm install n8n@2.26.2

yarn

yarn add n8n@2.26.2

pnpm

pnpm add n8n@2.26.2

Severity breakdown

CVSS 4.0 0.0

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

Attack vector: Network
Attack complexity: Low
Attack requirements: Present
Privileges required: None
User interaction: None
Confidentiality (vulnerable system): Low
Integrity (vulnerable system): Low
Availability (vulnerable system): None
Confidentiality (subsequent systems): Low
Integrity (subsequent systems): Low
Availability (subsequent systems): None

CVSS 3.1 7.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Weakness

CWE-290: Authentication Bypass by Spoofing

This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2026-54308

Packages

github.com/n8n-io/n8n

Timeline

Jun 16, 2026 Published
Oct 25, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-v98v-ff95-f3cp n8n Vulnerable to Remote Code Execution via Expression Injection	High Known exploited	Also affects n8n
GHSA-qgpw-8g46-w95v n8n: Git Node branch.<name>.remote Config Key Bypasses Sandbox Path Restriction, Enabling Local Git Repository Read	Medium	Also affects n8n
GHSA-65xw-2v52-jhxc n8n: Cross-User Active Workflow ID and Lifecycle Event Disclosure via Missing userId Filter	Medium	Also affects n8n
GHSA-pq6c-vh67-xpm3 n8n: Log Streaming Event Destinations Decrypt Generic-Auth Credentials Without Ownership Check	Medium	Also affects n8n
GHSA-cqr2-h44g-v75v n8n: Cross-Tenant Project-Member PII Disclosure via Missing Per-Project Scope Check on Role Assignment Endpoints	Medium	Also affects n8n
GHSA-pf83-w3f9-8m37 n8n: Disabled OIDC SSO Endpoints Remain Active and Issue Valid Sessions	Medium	Also affects n8n
GHSA-6xcw-7xm6-48c6 n8n: Expression Sandbox Escape via Shared Builtin Tampering and Code-Printer Injection Leads to Code Execution	High	Also affects n8n
GHSA-34ff-336r-5q23 n8n: Domain-Restriction Bypass via Unguarded Model-Search Endpoint in OpenAI Chat Model Node	Medium	Also affects n8n

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor