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

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

n8n CVE-2026-56353

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

CVE-2026-56353 has a CVSS 4.0 base score of 6.3 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/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.2%.

EUVD-2026-44626 MEDIUM

Improper Authentication (CWE-287)

2026-07-15 VulnCheck

GHSA-455f-pg36-wx7g

Authentication Bypass N8n

6.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

6.3 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/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

4.8 MEDIUM

Non-default n8n User Auth configuration required maps to AC:H; no credentials or interaction needed; impact limited to low read and write on workflow data only.

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

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

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jul 15, 2026 - 13:03 EUVD

Source Code Evidence Fetched

Jul 15, 2026 - 12:38 vuln.today

Analysis Generated

Jul 15, 2026 - 12:38 vuln.today

DescriptionCVE.org

n8n contains an authentication bypass in the Chat Trigger node when configured with n8n User Auth (a non-default configuration). In affected releases - before 1.123.22, the 2.0.0 through 2.9.2 line, and 2.10.0 - the authentication check on the Chat Trigger webhook endpoint can be circumvented, allowing access without valid credentials. Fixed in 1.123.22, 2.9.3, and 2.10.1.

AnalysisAI

Authentication bypass in the n8n Chat Trigger node allows unauthenticated network access to protected webhook endpoints when the node is explicitly configured with n8n User Auth - a non-default operator setting. Affected releases span all 1.x builds before 1.123.22, the entire 2.0.0-2.9.2 range, and 2.10.0. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; the CVSS 4.0 score of 6.3 with AT:P correctly reflects that real-world exposure is bounded by the non-default configuration prerequisite.

Technical ContextAI

n8n is a source-available workflow automation platform distributed as an npm package (cpe:2.3:a:n8n:n8n). Its Chat Trigger node exposes an HTTP webhook endpoint that external clients can invoke to drive conversational workflows. When an operator selects 'n8n User Auth' on that node, n8n is expected to validate caller credentials before processing the webhook. The root cause is CWE-287 (Improper Authentication): the credential validation logic on the Chat Trigger webhook handler contains a flaw that allows the check to be circumvented entirely, so the server proceeds as if authentication succeeded without verifying the supplied (or absent) credentials. The bug spans both the 1.x and 2.x release lines, indicating the flaw exists in shared webhook authentication middleware rather than version-specific code, as corroborated by two separate patch commits.

RemediationAI

Upgrade n8n to a patched release: version 1.123.22 or later for the 1.x line, version 2.9.3 or later for the 2.9.x line, or version 2.10.1 or later for the 2.10.x line. Vendor-released patches are confirmed in versions 1.123.22, 2.9.3, and 2.10.1. The underlying fixes are available in commits https://github.com/n8n-io/n8n/commit/062644ef786b6af480afe4a0f12bc6d70040534a and https://github.com/n8n-io/n8n/commit/1479aab2d32fe0ee087f82b9038b1035c98be2f6, and the advisory is at https://github.com/n8n-io/n8n/security/advisories/GHSA-jh8h-6c9q-7gmw. If immediate upgrade is not feasible, the vendor offers three partial mitigations with trade-offs: (1) Switch the Chat Trigger node to a different authentication method - this eliminates the vulnerable code path entirely and is the strongest workaround, but requires reconfiguring client integrations; (2) Restrict network access to the webhook endpoint to trusted IP ranges or origins - this reduces exposure to known callers but does not close the bypass for compromised trusted hosts; (3) Limit workflow creation and editing permissions to fully trusted users only - this reduces the likelihood of malicious workflows being created but does not prevent exploitation of existing exposed nodes. The vendor explicitly notes these workarounds do not fully remediate the risk.