dbcve.org
N8nApplication

CVE-2026-25053

CRITICAL · 9.9 CVSS v3.1 Published 2026-02-04
Fix available
A fix is available. Upgrade to 1.123.0 / 2.5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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 versions 1.123.10 and 2.5.0, vulnerabilities in the Git node allowed authenticated users with permission to create or modify workflows to execute arbitrary system commands or read arbitrary files on the n8n host. This issue has been patched in versions 1.123.10 and 2.5.0.

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

The Git node in n8n workflow automation platform versions prior to 1.123.10 and 2.5.0 contains vulnerabilities allowing authenticated users with workflow create/modify permissions to execute arbitrary system commands or read arbitrary files on the host through command injection and path traversal in the Git node.

MitigationUpgrade n8n to version 1.123.10 or 2.5.0. Review and audit workflows using the Git node for any signs of exploitation, and limit Git node permissions to only trusted users until patched.

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:< 1.123.0>= 2.0.0, < 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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify your n8n version
    Access the n8n UI and navigate to Settings > About to view the installed version, or check the version via your deployment method (docker image tag, package.json, or CLI if available
    Affected if The version is less than 1.123.0, or greater than or equal to 2.0.0 but less than 2.5.0
  2. Locate workflows using the Git node
    Search your workflow storage (database or filesystem depending on your setup) for workflows that include the Git node, or review workflows in the UI for any using the Git node
    Affected if You have active workflows that utilize the Git node functionality
  3. Review user permissions for workflow creation and modification
    Check your n8n user management settings to see which users or roles have workflow create or modify permissions
    Affected if There are users other than administrators with workflow create or modify permissions who could access the Git node
  4. Inspect Git node configurations in use
    For workflows using the Git node, examine the node configuration parameters such as repository URL, branch, commands, and any fields that accept user input that could be manipulated
    Affected if Git node configurations accept dynamic input that could potentially be exploited for command injection or path traversal

You are affected if your n8n version falls within the vulnerable ranges AND you have workflows using the Git node accessible to users with workflow create/modify permissions.

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 1.123.0 / 2.5.0 or later
Fixed in 1.123.02.5.0
Vendor patch github.com →
Interim mitigation

Upgrade n8n to version 1.123.10 or 2.5.0. Review and audit workflows using the Git node for any signs of exploitation, and limit Git node permissions to only trusted users until patched.

Recommended fix High confidence

Upgrade to n8n version 1.123.10 (if on 1.x branch) or version 2.5.0 (if on 2.x branch)

  1. 1. Back up your current n8n instance, including workflows, credentials, and configuration
  2. 2. Identify your current n8n version using `n8n --version` or your deployment method
  3. 3. If running version 1.x: Upgrade to version 1.123.10 or later
  4. 4. If running version 2.x: Upgrade to version 2.5.0 or later
  5. 5. For Docker: Update your image tag to `n8nio/n8n:1.123.10` or `n8nio/n8n:2.5.0` and recreate the container
  6. 6. For npm: Run `npm install -g [email protected]` or `npm install -g [email protected]`
  7. 7. Verify the upgrade was successful by checking the n8n version
  8. 8. Review and test workflows that use the Git node to ensure functionality is intact
Caveat Review release notes for your target version branch as there may be workflow or configuration changes between major/minor versions

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

Fix this in N8n Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25053 — 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-25053 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