Skip to main content
← All vulnerabilities
CVE-2026-119557EUVD-2026-113822GHSA-4QWQ-628R-75JR

n8n from 2.14.0 through 2.46.3 Path Traversal via Databricks Node

Affects n8n 2.14.0 through 2.46.3 when the Databricks node's Genie getSpace operation is used. No vendor rating or fixed version is listed in the checked facts.

Published
Last modified
published
Not listed in CISA KEV
Unclear
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

n8n from 2.14.0 through 2.46.3 contains a path traversal vulnerability in the Databricks node that allows unauthenticated attackers to reach arbitrary Databricks API endpoints by injecting unencoded resource identifiers. Attackers can supply ../ sequences and query strings via webhook, chat, or form inputs mapped to spaceId, indexName, or filePath to read secrets using the stored credential.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • n8n-io n8n

    From 2.14.0 · through 2.46.3

References 8

GitHub · n8n-io/n8n

abraxaslabs.tech

vulncheck.com

FAQ

Questions about CVE-2026-119557

What does this mean?

The Databricks node's Genie getSpace operation places the spaceId parameter into the request URL without encoding it, which is the path traversal weakness named in the title. The checked facts do not describe the impact beyond this.Source: github.com

Am I affected, and how do I check?

n8n versions 2.14.0 through 2.46.3 are listed as affected, and the code path is the Databricks node's Genie getSpace operation. To check a setup, look at the installed n8n version and whether a workflow uses the Databricks node with the Genie getSpace operation.Source: github.com

What should I do about it?

The checked facts do not list a fixed version, so no upgrade target is given. Check the n8n project's release notes or advisory for a fixed release.Source: github.com

Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What if there's no patch?

The checked facts give no workaround. Limiting use of the Databricks node's Genie getSpace operation is the only mitigation the facts point to, but no specific steps are documented in them.Source: github.com