dbcve.org
N8nApplication

CVE-2026-44790

HIGH · 8.8 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 1.123.43 / 2.20.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 1.123.43, 2.22.1, and 2.20.7, an authenticated user with permission to create or modify workflows could inject CLI flags on the Git node's Push operation allowing an attacker to read arbitrary files from the n8n server potentially leading to full compromise. This vulnerability is fixed in 1.123.43, 2.22.1, and 2.20.7.

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

Authenticated users with workflow create/modify permissions can inject CLI flags into the Git node's Push operation, enabling arbitrary file read from the n8n server via path traversal. This leads to potential full system compromise through file disclosure.

MitigationUpdate n8n to version 1.123.43, 2.22.1, or 2.20.7 or later. Additionally, review and restrict workflow permissions for untrusted users.

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.43>= 2.0.0, < 2.20.7>= 2.21.0, < 2.22.1

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Determine installed n8n version
    Check the version via the n8n UI (Settings > About), CLI (n8n --version), or the package.json file in the n8n installation directory
    Affected if The installed version is less than 1.123.43, OR between 2.0.0 and 2.20.6 inclusive, OR between 2.21.0 and 2.22.0 inclusive
  2. Identify workflows using the Git node
    Review your n8n workflows and search for nodes of type Git, specifically those using the Push operation
    Affected if Any active or accessible workflow uses the Git node with Push functionality
  3. Verify user permission configuration
    Check the roles and permissions assigned to users in n8n, specifically looking for users granted workflow create or workflow modify permissions
    Affected if Untrusted or low-privilege users have workflow create or workflow modify permissions enabled
  4. Confirm Git node is accessible to standard users
    Test whether users with workflow create/modify permissions can access and configure the Git node in the workflow editor
    Affected if Standard users can add or modify a Git node and access its Push operation settings

You are affected if your n8n version falls within the vulnerable ranges AND untrusted users have workflow create/modify permissions AND workflows can include the Git node's Push operation.

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.43 / 2.20.7 / 2.22.1 or later
Fixed in 1.123.432.20.72.22.1
Interim mitigation

Update n8n to version 1.123.43, 2.22.1, or 2.20.7 or later. Additionally, review and restrict workflow permissions for untrusted users.

Recommended fix High confidence

1.123.43 (for 1.x users), 2.20.7 (for 2.0.0-2.20.x users), or 2.22.1 (for 2.21.0-2.22.0 users)

  1. Identify your current n8n version by checking the n8n instance or Docker container
  2. Determine which version branch you are on (1.x or 2.x)
  3. Backup your n8n database and configuration files before upgrading
  4. If running 1.x (< 1.123.43): Upgrade to version 1.123.43 or later
  5. If running 2.0.0-2.20.x: Upgrade to version 2.20.7 or later
  6. If running 2.21.0-2.22.0: Upgrade to version 2.22.1 or later
  7. After upgrade, verify the n8n instance is running the patched version
  8. Test that the Git node works normally with the Push operation
Caveat Standard upgrade risks apply - test in staging first, backup database, review breaking changes in n8n release notes between your current and target version

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

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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