dbcve.org
N8nApplication

CVE-2026-33724

HIGH · 7.4 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 2.5.0 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
n8n is an open source workflow automation platform. Prior to version 2.5.0, 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). The issue has been fixed in n8n version 2.5.0. Users should upgrade to this version or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Disable the Source Control feature if it is not actively required, and/or 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In n8n versions prior to 2.5.0, the Source Control feature when configured to use SSH explicitly disables host key verification in the SSH command used for git operations. This allows a network attacker positioned between the n8n instance and the remote Git server to perform a man-in-the-middle attack, presenting a fraudulent host key to intercept connections and potentially inject malicious content into workflows or exfiltrate repository data.

MitigationUpgrade n8n to version 2.5.0 or later. If immediate upgrade is not feasible, temporarily disable the Source Control feature or ensure n8n communicates with the Git server only over trusted, controlled network paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N8nApplication
Affected:< 2.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed n8n version
    Query the n8n API endpoint /health or check the docker container version, or run 'npm list n8n' in the installation directory
    Affected if Version is below 2.5.0
  2. Verify Source Control feature is enabled
    Check n8n settings or environment configuration for Source Control / git integration settings
    Affected if Source Control feature is actively configured and in use
  3. Confirm SSH is configured as the Git transport
    Inspect the Source Control configuration to determine if the Git remote URL uses SSH (git@hostname:...) rather than HTTPS
    Affected if SSH protocol is selected for the Git remote connection

You are affected if n8n version is below 2.5.0 AND Source Control is enabled using SSH protocol, as this combination allows man-in-the-middle attacks on git operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.5.0 or later
Fixed in 2.5.0
Interim mitigation

Upgrade n8n to version 2.5.0 or later. If immediate upgrade is not feasible, temporarily disable the Source Control feature or ensure n8n communicates with the Git server only over trusted, controlled network paths.

Recommended fix High confidence

2.5.0

  1. Upgrade n8n to version 2.5.0 or later to remediate the SSH host key verification vulnerability
  2. Verify the upgrade was successful by checking the n8n version after installation
  3. If upgrading is not immediately possible, disable the Source Control feature if it is not actively required
  4. If upgrading is not immediately possible, restrict network access to ensure the n8n instance communicates with the Git server only over trusted, controlled network paths

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33724 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data