dbcve.org
N8nApplication

CVE-2026-44792

CRITICAL · 9.0 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

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 attacker with write access to the git repository connected to an n8n Source Control configuration could commit a malicious Data Table JSON file containing a crafted column name. When an administrator performed a Source Control Pull, n8n imported the file and could lead to SQL injection on the internal PostgreSQL instance. Exploitation requires the n8n instance uses PostgreSQL as its database backend, the Source Control feature is enabled and connected to a repository the attacker can write to, and an administrator triggers a Source Control Pull. 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

SQL injection vulnerability in n8n's Source Control Pull functionality. An attacker with write access to the connected git repository can commit a malicious Data Table JSON file containing a crafted column name that, when imported during a Source Control Pull, leads to SQL injection in the PostgreSQL backend.

MitigationUpgrade n8n to version 1.123.43, 2.22.1, or 2.20.7 or later. Alternatively, disable Source Control or ensure only trusted users have write access to the connected repository.

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 installed n8n version
    Run `n8n --version` or check the version displayed in the n8n UI (usually shown in the bottom-left corner of the interface)
    Affected if The installed version falls within any of these ranges: < 1.123.43, >= 2.0.0 and < 2.20.7, or >= 2.21.0 and < 2.22.1
  2. Confirm Source Control is enabled
    Navigate to Settings > Source Control in the n8n UI, or check if a `.n8n` git repository folder exists in your project directory
    Affected if Source Control is enabled and a git repository is connected
  3. Identify the database backend
    Check your n8n configuration file (typically `~/.n8n/config` or environment variable `DB_TYPE`) to see which database n8n is using
    Affected if The backend database is PostgreSQL (the SQL injection affects the PostgreSQL backend specifically)
  4. Assess git repository access controls
    Review who has write access to the connected git repository by checking repository settings, team permissions, or branch protection rules
    Affected if Any untrusted users or external contributors have write access to the repository

You are affected if your n8n version is within the vulnerable ranges AND Source Control is enabled with a connected git repository AND PostgreSQL is used as the backend AND untrusted users have write access to that repository.

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

Upgrade n8n to version 1.123.43, 2.22.1, or 2.20.7 or later. Alternatively, disable Source Control or ensure only trusted users have write access to the connected repository.

Recommended fix High confidence

Upgrade to 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.x users)

  1. 1. Identify the current n8n version running in your environment
  2. 2. Determine which major version line (1.x or 2.x) you are currently using
  3. 3. For 1.x users: Upgrade to version 1.123.43 or later
  4. 4. For 2.0.0-2.20.x users: Upgrade to version 2.20.7 or later
  5. 5. For 2.21.x users: Upgrade to version 2.22.1 or later
  6. 6. After upgrade, verify the Source Control functionality works correctly
  7. 7. Review any post-upgrade logs for errors

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

Fix this in N8n Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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