dbcve.org
N8nApplication

CVE-2026-49465

HIGH · 7.7 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 1.123.48 / 2.21.8 or later.
See remediation →
83/100
Remediation priority · High
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.48, 2.21.8, and 2.22.4, an authenticated user with permission to create or modify workflows could supply a local filesystem path as the source repository in the Git node's Clone operation, or as the target repository in the Push operation, bypassing the N8N_RESTRICT_FILE_ACCESS_TO file sandbox. This allowed the contents of any local git repository accessible to the n8n process to be cloned into an allowed path and read, circumventing the access restrictions that correctly blocked direct file reads to the same paths. This vulnerability is fixed in 1.123.48, 2.21.8, and 2.22.4.

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 1.123.48, 2.21.8, and 2.22.4, an authenticated user with workflow create/modify permissions could supply local filesystem paths as Git repository sources (Clone) or targets (Push) in the Git node, bypassing the N8N_RESTRICT_FILE_ACCESS_TO file sandbox. This allowed reading contents of any local git repository accessible to the n8n process by leveraging git operations instead of direct file reads, circumventing the sandbox restrictions.

MitigationUpgrade n8n to version 1.123.48, 2.21.8, 2.22.4 or later to patch the sandbox bypass in the Git node.

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.48>= 2.0.0, < 2.21.8>= 2.22.0, < 2.22.4

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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
    Run `n8n --version` or check the version in the UI/environment variables to identify the exact version running
    Affected if Version is < 1.123.48, or >= 2.0.0 and < 2.21.8, or >= 2.22.0 and < 2.22.4
  2. Verify Git node is accessible
    Check if the Git node is enabled and available in the n8n instance by reviewing installed nodes or attempting to create a workflow with the Git node
    Affected if Git node is available and users can access it to create or modify workflows
  3. Identify users with workflow create/modify permissions
    Review user roles and permissions in n8n to determine which authenticated users have workflow create or workflow modify access
    Affected if Any authenticated users have workflow create or modify permissions, allowing them to configure the Git node with arbitrary paths
  4. Check N8N_RESTRICT_FILE_ACCESS_TO configuration
    Review environment variables or configuration to see if N8N_RESTRICT_FILE_ACCESS_TO is set (this sandbox can be bypassed by the vulnerability)
    Affected if The sandbox is configured but can be bypassed through the Git node as described in the CVE

The environment is affected if n8n version falls within the vulnerable ranges AND the Git node is accessible to users with workflow create/modify permissions, regardless of N8N_RESTRICT_FILE_ACCESS_TO configuration since the sandbox can be circumvented.

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.48 / 2.21.8 / 2.22.4 or later
Fixed in 1.123.482.21.82.22.4
Interim mitigation

Upgrade n8n to version 1.123.48, 2.21.8, 2.22.4 or later to patch the sandbox bypass in the Git node.

Recommended fix High confidence

1.123.48 (for 1.x) OR 2.21.8 (for 2.0.0-2.21.x) OR 2.22.4 (for 2.22.x)

  1. Identify which major version branch (1.x or 2.x) your n8n instance is currently running
  2. For 1.x users: Upgrade to version 1.123.48 or later
  3. For 2.0.0-2.21.x users: Upgrade to version 2.21.8 or later
  4. For 2.22.x users: Upgrade to version 2.22.4 or later
  5. If using a containerized deployment, update the image tag in your docker-compose.yml or container orchestration config
  6. After upgrade, verify the Git node behavior to confirm the path traversal protection is active
  7. Ensure N8N_RESTRICT_FILE_ACCESS_TO is still properly configured for defense-in-depth
Caveat No breaking changes mentioned in the advisory; standard version upgrade precautions apply

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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