What is GHSA-jvc7-762p-3743?

GHSA-jvc7-762p-3743 is a security advisory published by GitHub Security Advisories with Medium severity. n8n: Missing Token Validation on Microsoft Agent 365 Trigger and Stripe Nodes

Which CVE IDs does GHSA-jvc7-762p-3743 cover?

GHSA-jvc7-762p-3743 covers the following CVE IDs: CVE-2026-54308. Each CVE has its own detail page on EchelonGraph Pulse with the synthesized EG score.

What is the CVSS v3 score of GHSA-jvc7-762p-3743?

GHSA-jvc7-762p-3743 has a CVSS v3 base score of 7.2, published by GitHub Security Advisories.

Which products are affected by GHSA-jvc7-762p-3743?

GHSA-jvc7-762p-3743 affects 2 products, including: npm/n8n:\u003e= 2.26.0, \u003c 2.26.2; npm/n8n:\u003c 2.25.7.

GHSA-jvc7-762p-3743MediumCVSS 7.2

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

Vendor

GitHub Security Advisories

Published

June 16, 2026

Last Modified

June 16, 2026

🔗 CVE IDs covered (1)

CVE-2026-54308 →

📋 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 products2

npm/n8n:>= 2.26.0, < 2.26.2
npm/n8n:< 2.25.7