n8n: Execute Command Node Allows Authenticated Users to Run Arbitrary Commands on Host
CVE-2025-71380GHSA-365g-vjw2-grx8
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm n8n-nodes-base
- Affected
- <= 1.113.0
- Fixed in
- no fixed version recorded
npm n8n
- Affected
- <= 1.114.4
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-365g-vjw2-grx8 lists affected ranges: npm n8n-nodes-base >=0 =0 <=1.114.4
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-365g-vjw2-grx8 lists affected ranges: npm n8n-nodes-base >=0 =0 <=1.114.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2025-71380: 0.57% estimated exploitation activity in the next 30 days; percentile 47.27 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact The Execute Command node in n8n allows execution of arbitrary commands on the host system where n8n runs. While this functionality is intended for advanced automation and can be useful in certain workflows, it poses a security risk if all users with access to the n8n instance are not fully trusted. An attacker—either a malicious user or someone who has compromised a legitimate user account—could exploit this node to run arbitrary commands on the host machine, potentially leading to data exfiltration, service disruption, or full system compromise. This vulnerability affects all n8n deployments where: - The Execute Command node is enabled, and - Not all user accounts are strictly controlled and trusted. n8n.cloud is not impacted. Patches No code changes have been made to alter the behavior of the Execute Command node. The recommended mitigation is to disable the node by default in environments where it is not explicitly required. Future n8n versions may change the default…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-365g-vjw2-grx8
- Revision 1 · created ·
Published from osv record GHSA-365g-vjw2-grx8
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-71380 Advisory: n8n: Execute Command Node Allows Authenticated Users to Run Arbitrary Commands on Host IDs: CVE-2025-71380, GHSA-365g-vjw2-grx8 Record: https://patchnext.com/advisories/cve-2025-71380 (revision 2, source checked 26 Oct 2026, 12:38 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm n8n-nodes-base: affected <= 1.113.0 - npm n8n: affected <= 1.114.4 ## Suggested inspection (read-only) - `npm ls n8n-nodes-base --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. - `npm ls n8n --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on n8n-nodes-base, n8n. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-365g-vjw2-grx8 (OSV record GHSA-365g-vjw2-grx8 lists affected ranges: npm n8n-nodes-base >=0 =0 <=1.114.4) - Verified: https://github.com/advisories/GHSA-365g-vjw2-grx8 (GitHub-reviewed advisory GHSA-365g-vjw2-grx8 lists affected ranges: npm n8n-nodes-base >=0 =0 <=1.114.4) Commands are suggestions: review each one before running it.
Loading voting…