CVE-2026-33724: N8n Remote Code Execution Vulnerability

MODERATE
Advisory Identifier: GHSA-43v7-fp2v-68f6
Share
CVSS 5.4
CWE-639
Published
Advisory Summary

CVE-2026-33724 is a MODERATE (CVSS 5.4) remote code execution vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting N8n libraries in the npm ecosystem. The issue involves n8n's source control ssh configuration uses stricthostkeychecking=no. Remediation is available by upgrading affected packages to version 2.5.0.

CVE-2026-33724 at a Glance

CVE Identifier CVE-2026-33724
GHSA Identifier GHSA-43v7-fp2v-68f6
Severity MODERATE
CVSS v3.1 Base Score 5.4
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product N8n
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 5.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-33724

To remediate this vulnerability, upgrade all affected N8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n fixed: 2.5.0 
npm install n8n@2.5.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls n8n

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-33724, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of N8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.5.0), your application is affected.

Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In N8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impact When the Source Control feature is configured to use SSH, the SSH command used for git operations explicitly disabled host key verification. A network attacker positioned between the n8n instance and the remote Git server could intercept the connection and present a fraudulent host key, potentially injecting malicious content into workflows or intercepting repository data. - This issue only affects instances where the Source Control feature has been explicitly enabled and configured to use SSH (non-default). ## Patches The issue has been fixed in n8n version 2.5.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: - Disable the Source Control feature if it is not actively required. - Restrict network access to ensure the n8n instance communicates with the Git server only over trusted, controlled network paths. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

CVE-2026-33724 Affected N8n Versions

1 component(s)
Fixed Versions:
2.5.0
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm/n8n
npm
< 2.5.0
2.5.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/n8n-io/n8n/security/advisories/GHSA-43v7-fp2v-68f6
NVD — CVE-2026-33724 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-33724
N8n Source Repository REPOSITORY
https://github.com/n8n-io/n8n

Frequently Asked Questions

What is CVE-2026-33724?
CVE-2026-33724 is a security vulnerability in N8n involving n8n's Source Control SSH Configuration Uses StrictHostKeyChecking=no under CWE-639: Authorization Bypass Through User-Controlled Key.
Which N8n versions are affected?
Affected versions include releases prior to 2.5.0 across affected packages: n8n.
What version fixes CVE-2026-33724?
Upgrading to 2.5.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 2.5.0. Upgrade your dependency to 2.5.0 or later.
What is the CVSS score of CVE-2026-33724?
CVE-2026-33724 has a CVSS v3.1 base score of 5.4 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N.
What CWE is associated with CVE-2026-33724?
CVE-2026-33724 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check npm dependencies for CVE-2026-33724?
Run the dependency tree command: 'npm ls n8n'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-43v7-fp2v-68f6",
  "modified" : "2026-03-25T22:06:10Z",
  "published" : "2026-03-25T22:06:10Z",
  "aliases" : [ "CVE-2026-33724" ],
  "summary" : "n8n's Source Control SSH Configuration Uses StrictHostKeyChecking=no",
  "details" : "## Impact\nWhen the Source Control feature is configured to use SSH, the SSH command used for git operations explicitly disabled host key verification. A network attacker positioned between the n8n instance and the remote Git server could intercept the connection and present a fraudulent host key, potentially injecting malicious content into workflows or intercepting repository data.\n\n- This issue only affects instances where the Source Control feature has been explicitly enabled and configured to use SSH (non-default).\n\n## Patches\nThe issue has been fixed in n8n version 2.5.0. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Disable the Source Control feature if it is not actively required.\n- Restrict network access to ensure the n8n instance communicates with the Git server only over trusted, controlled network paths.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.5.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-43v7-fp2v-68f6"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33724"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-25T22:06:10Z",
    "nvd_published_at" : "2026-03-25T19:16:51Z"
  }
}