Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-44792: n8n: Source Control Pull SQL Injection

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No special conditions are required; it is repeatable.
  • Fixed version: n8n-io n8n 1.123.43.

Low priority for now. Upgrade to n8n-io n8n 1.123.43 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.9 · v4.0—No exploit Fix available
Published
Jun 23, 2026
Updated
Oct 26, 2026
EPSS
0.3% · 32th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
8.9
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-44792

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for n8n records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
n8nn8n

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • n8n n8nbefore 1.123.43
  • n8n n8n2.0.0 and later · before 2.20.7
  • n8n n8n2.21.0 and later · before 2.22.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • n8n-io n8n

    • < 1.123.43, >= 2.0.0-rc.0, < 2.20.7, >= 2.21.0, < 2.21.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmn8nfrom 2.0.0-rc.0 · before 2.20.72.20.7
npmn8nfrom 2.21.0 · before 2.21.12.21.1
npmn8nbefore 1.123.431.123.43

Same product

n8n: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-68613n8n Vulnerable to Remote Code Execution via Expression InjectionKEV
    95Now
  • CVE-2026-21858n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling
    63This week
  • CVE-2026-1470Authenticated users can bypass the Expression sandbox mechanism to achieve full remote code execution on n8n’s main node.
    45Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-44790Jun 23, 2026 · n8n: Arbitrary File Read via Git Node
    37Monitor
  • ← EarlierCVE-2026-44791Jun 23, 2026 · n8n: XML Node Prototype Pollution Patch Bypass
    37Monitor
  • Later →CVE-2026-45732Jun 23, 2026 · n8n: Cross-user Authorization Bypass in Dynamic Credential OAuth Endpoints
    33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
n8n-io n8n1.123.43 · descriptionVendor (CNA)
npm:n8n1.123.43Package registry (OSV)
npm:n8n2.20.7Package registry (OSV)
npm:n8n2.21.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-27497118 days apartn8n has Potential Remote Code Execution via Merge Node
    37Monitor
  • CVE-2026-3371390 days apartn8n Vulnerable to SQL Injection in Data Table Node via orderByColumn Expression
    34Monitor
  • CVE-2026-7707158 days apartn8n before 1.123.69 PostgREST Filter Injection via Supabase
    28Monitor
  • CVE-2026-543100 days apartn8n: SQL Injection in Postgres v1/TimesclaeDB Nodes
    26Monitor
  • CVE-2026-543130 days apartn8n: NoSQL Injection in MongoDB Node Find And Replace Operation
    26Monitor
  • CVE-2026-7277549 days apartn8n before 1.123.67 SQL Injection via PostgresTrigger Node
    23Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
A
Scope
X

Weakness class (CWE)

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

The bug in code

The whole CWE-89 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = '" + owner + "'");

Fixed

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = $1",  [owner]);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records