Is there a patch available for CVE-2026-54303?

Yes, a patch is available for CVE-2026-54303. Update the affected software to the latest version immediately.

n8n CVE-2026-54303

Q: What is the CVSS score of CVE-2026-54303?

CVE-2026-54303 has a CVSS 4.0 base score of 6.8 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-38460 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-06-16 https://github.com/n8n-io/n8n

GHSA-h86q-fx34-gfjr

XSS Microsoft

6.8

CVSS 4.0 · Vendor: https://github.com/n8n-io/n8n

Severity by source

Vendor (https://github.com/n8n-io/n8n) PRIMARY

6.8 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

7.6 HIGH

Network-accessible webhook endpoint (AV:N/AC:L) reflects attacker input to authenticated victim browser (PR:L/UI:R), with scope change enabling cross-context credential theft (S:C/C:H); limited integrity impact from constrained JavaScript execution, no availability impact.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (https://github.com/n8n-io/n8n).

CVSS VectorVendor: https://github.com/n8n-io/n8n

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Scope

Lifecycle Timeline

CVSS changed

Jun 23, 2026 - 17:07 NVD

7.6 (MEDIUM) 6.8 (MEDIUM)

Source Code Evidence Fetched

Jun 17, 2026 - 00:34 vuln.today

Analysis Generated

Jun 17, 2026 - 00:34 vuln.today

CVE Published

Jun 16, 2026 - 22:39 github-advisory

MEDIUM 7.6

DescriptionCVE.org

Impact

An endpoint in the Meta and Microsoft Teams trigger nodes reflects a query parameter into the HTTP response without sanitization or Content-Security-Policy headers, enabling reflected XSS in the n8n origin when a logged-in user visits a crafted URL.

Patches

The issue has been fixed in n8n version 2.24.0. Users should upgrade to this version or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

Limit workflow creation and activation permissions to fully trusted users only.
Disable the affected nodes by adding n8n-nodes-base.facebookTrigger, n8n-nodes-base.whatsAppTrigger, n8n-nodes-base.facebookLeadAdsTrigger, and n8n-nodes-base.microsoftTeamsTrigger to the NODES_EXCLUDE environment variable.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

AnalysisAI

Reflected XSS in n8n's Facebook (Meta), WhatsApp, and Microsoft Teams webhook trigger nodes allows an attacker to execute arbitrary JavaScript in an authenticated user's browser by luring them to a crafted URL targeting the vulnerable webhook verification endpoints. Affected are all n8n deployments running version < 2.24.0 with any of the four vulnerable trigger nodes active; the CVSS scope change (S:C) means successful exploitation extends beyond the n8n component itself, enabling session hijacking or theft of API credentials stored in workflows. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor-released patch is confirmed in n8n 2.24.0.

Technical ContextAI

n8n is an open-source workflow automation platform distributed as an npm package (pkg:npm/n8n). It supports webhook-based trigger nodes that expose HTTP endpoints used by third-party platforms - including Meta (Facebook, WhatsApp) and Microsoft Teams - to perform webhook subscription verification challenges. These verification endpoints accept and reflect query parameters in their HTTP responses, which is required by the third-party platforms to validate the webhook handshake. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation): the reflected query parameters are not sanitized or HTML-encoded before being written into the HTTP response, and no Content-Security-Policy headers are set to block inline script execution. This classic reflected XSS pattern means any query parameter value controlled by an attacker is returned verbatim in the response body and executed as JavaScript in the victim's browser. The CVSS scope change (S:C) reflects that exploitation escapes the n8n application boundary into the broader browser security context, enabling cross-origin data access and session manipulation.

RemediationAI

The primary remediation is to upgrade n8n to version 2.24.0 or later, which is the vendor-confirmed fixed release per advisory GHSA-h86q-fx34-gfjr (https://github.com/n8n-io/n8n/security/advisories/GHSA-h86q-fx34-gfjr). If immediate upgrade is not feasible, two temporary mitigations are available with trade-offs: first, restrict workflow creation and activation permissions to fully trusted users only - this reduces the chance that a low-privileged attacker can activate vulnerable nodes but does not close the endpoint if nodes are already active, and has no effect if the targeted victim is an admin. Second, disable all four vulnerable nodes by setting the environment variable NODES_EXCLUDE to include n8n-nodes-base.facebookTrigger, n8n-nodes-base.whatsAppTrigger, n8n-nodes-base.facebookLeadAdsTrigger, and n8n-nodes-base.microsoftTeamsTrigger - this eliminates the vulnerable endpoints entirely but will break all existing workflows relying on Meta or Microsoft Teams webhook triggers. The vendor explicitly states neither workaround fully remediates the risk and both should be treated as short-term measures only until upgrade to 2.24.0 is completed.