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

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

n8n CVE-2026-56777

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

CVE-2026-56777 has a CVSS 4.0 base score of 5.3 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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-40453 MEDIUM

Incomplete List of Disallowed Inputs (CWE-184)

2026-06-30 VulnCheck

GHSA-x2rh-rhm8-cv8v

Python Information Disclosure N8n

5.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

5.3 MEDIUM

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

4.3 MEDIUM

Authenticated workflow editor required (PR:L); confidentiality limited to env vars in runner process (C:L); no integrity or availability impact; scope unchanged.

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

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

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jul 01, 2026 - 02:16 EUVD

Analysis Generated

Jun 30, 2026 - 23:21 vuln.today

DescriptionCVE.org

n8n before 2.25.7 and 2.26.x before 2.26.2 contains an abstract syntax tree (AST) security validator bypass in the Python Code node. An authenticated user with permission to create or modify workflows containing a Python Code node can bypass the validator and access the task executor module namespace. The issue only affects self-hosted instances where the Python Task Runner is enabled; where N8N_BLOCK_RUNNER_ENV_ACCESS is configured to allow it, this can disclose environment variables accessible to the task runner process.

AnalysisAI

The Python Code node in n8n allows authenticated workflow editors to bypass the AST security validator by crafting Python code that evades an incomplete blocklist (CWE-184), reaching the task executor module namespace. Affected self-hosted n8n deployments running versions before 2.25.7 or 2.26.x before 2.26.2 with the Python Task Runner enabled are exposed to environment variable disclosure when N8N_BLOCK_RUNNER_ENV_ACCESS is not set to restrict access, potentially leaking API keys, database credentials, or other secrets injected at process startup. No public exploit code exists and no active exploitation has been confirmed at time of analysis.

Technical ContextAI

n8n is an open-source workflow automation platform that supports user-defined logic in Code nodes, including a Python Code node executed by a dedicated Python Task Runner subprocess. To restrict dangerous operations in user-supplied scripts, n8n implements an AST-based security validator that inspects the parsed syntax tree before execution. CWE-184 (Incomplete List of Disallowed Inputs) is the root cause: the validator's blocklist does not enumerate all code paths capable of reaching the task executor's module namespace, so a crafted AST node that is not on the blocklist passes validation and executes with runner-level access. The Python Task Runner operates as a separate process whose environment may contain secrets propagated via environment variables at process startup. The CPE identifier cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:* covers all n8n application versions across all platforms.

RemediationAI

Upgrade n8n to version 2.25.7 or later on the 2.25.x track, or to 2.26.2 or later on the 2.26.x track, per the vendor security advisory at https://github.com/n8n-io/n8n/security/advisories/GHSA-jwm3-qcfw-c5pp. If an immediate upgrade is not feasible, set the N8N_BLOCK_RUNNER_ENV_ACCESS environment variable to its restrictive value to prevent the task runner from exposing environment variables to user code - this eliminates the primary sensitive-data disclosure path without disabling the runner entirely, though it may affect workflows that intentionally consume environment variables. Alternatively, disabling the Python Task Runner feature entirely removes all attack surface for this vulnerability but prevents use of Python Code nodes. Restricting workflow-create and workflow-edit permissions to a minimal set of trusted users reduces the attacker pool but does not remediate the underlying validator bypass.