BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-86079High confidence

n8n: Path Injection in Elasticsearch and ElasticSecurity Nodes via Unencoded Identifiers

n8n-io · n8n

Official source article: GitHub GHSA-F2CP-M7MV-8JPV ↗. Check the applicable product and release in the original source.

6.3MediumCVSS 4.0
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Mitigation available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.49% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs n8n-io n8n and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges6 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmn8n< 1.123.761.123.76GitHub advisory ↗upstream repository advisory · 10 Sep 2026
npmn8n>= 2.38.0, < 2.38.22.38.2GitHub advisory ↗upstream repository advisory · 10 Sep 2026
npmn8n>= 2.0.0, < 2.37.72.37.7GitHub advisory ↗upstream repository advisory · 10 Sep 2026
npmn8nSEMVER: introduced 0; fixed 1.123.761.123.76OSV record ↗aggregator derived · 10 Sep 2026
npmn8nSEMVER: introduced 2.38.0; fixed 2.38.22.38.2OSV record ↗aggregator derived · 10 Sep 2026
npmn8nSEMVER: introduced 2.0.0; fixed 2.37.72.37.7OSV record ↗aggregator derived · 10 Sep 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-74277

No EUVD known-exploited evidence

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the Elasticsearch and ElasticSecurity nodes interpolated workflow-controlled index and document identifiers directly into REST request paths. An identifier containing path separators or dot segments could select another index or a cluster administration endpoint under the stored Elasticsearch credential. The affected request construction includes packages/nodes-base/nodes/Elastic/Elasticsearch/GenericFunctions.ts and the missing toPathSegment encoding. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
6.3 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Mitigation available
01

What, why and how

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the Elasticsearch and ElasticSecurity nodes interpolated workflow-controlled index and document identifiers directly into REST request paths. An identifier containing path separators or dot segments could select another index or a cluster administration endpoint under the stored Elasticsearch credential. The affected request construction includes packages/nodes-base/nodes/Elastic/Elasticsearch/GenericFunctions.ts and the missing toPathSegment encoding. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.

What

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the Elasticsearch and ElasticSecurity nodes interpolated workflow-controlled index and document identifiers directly into REST request paths. An identifier containing path separators or dot segments could select another index or a cluster administration endpoint under the stored Elasticsearch credential. The affected request construction includes packages/nodes-base/nodes/Elastic/Elasticsearch/GenericFunctions.ts and the missing toPathSegment encoding. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.

Why

Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the Elasticsearch and ElasticSecurity nodes interpolated workflow-controlled index and document identifiers directly into REST request paths. An identifier containing path separators or dot segments could select another index or a cluster administration endpoint under the stored Elasticsearch credential. The affected request construction includes packages/nodes-base/nodes/Elastic/Elasticsearch/GenericFunctions.ts and the missing toPathSegment encoding. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.

Why

Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-22 ↗

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCHighSubsequent-system confidentiality: A successful attack can cause a major loss.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkCWE-22
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-74277Official EUVD mapping

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the Elasticsearch and ElasticSecurity nodes interpolated workflow-controlled index and document identifiers directly into REST request paths. An identifier containing path separators or dot segments could select another index or a cluster administration endpoint under the stored Elasticsearch credential. The affected request construction includes packages/nodes-base/nodes/Elastic/Elasticsearch/GenericFunctions.ts and the missing toPathSegment encoding. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3165n8n: Mehrere Schwachstellen

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um Sicherheitsmechanismen zu umgehen, beliebigen Code auszuführen oder einen Denial of Service zu verursachen.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-033327n8nにおけるパストラバーサルの脆弱性

n8nはオープンソースのワークフロー自動化プラットフォームです。バージョン1.123.76、2.37.7、および2.38.2以前のElasticsearchおよびElasticSecurityノードは、ワークフロー制御下のインデックスおよびドキュメント識別子をRESTリクエストのパスに直接埋め込んでいました。パス区切り文字やドットセグメントを含む識別子によって、保存されたElasticsearchクレデンシャルのもとで別のインデックスやクラスタ管理エンドポイントが選択される可能性がありました。影響を受けるリクエストの構築は、packages/nodes-base/nodes/Elastic/Elasticsearch/GenericFunctions.tsファイル内のtoPathSegmentエンコーディングが欠落している箇所に含まれています。この問題はバージョン1.123.76、2.37.7、および2.38.2で修正されています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Mitigation available
Affected
n8n: >= 2.38.0, < 2.38.2, >= 2.0.0, < 2.37.7, < 1.123.76
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Apply the mitigation in the linked authoritative guidance while planning the vendor's permanent fix.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
Official vendor articles4 stored documents

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

  • Release n8n@1.123.76 · n8n-io/n8n · GitHub →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026n8n-io / n8n Public Notifications You must be signed in to change notification settings Fork 60.9k Star 206k Code Issues 358 Pull requests 751 Actions Security and quality 196 Insights Additional navigation options Code Issues Pull requests Actions Security and quality Insights n8n@1.123.76 Compare Cho
  • Release n8n@2.37.7 · n8n-io/n8n · GitHub →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026n8n-io / n8n Public Notifications You must be signed in to change notification settings Fork 60.9k Star 206k Code Issues 358 Pull requests 751 Actions Security and quality 196 Insights Additional navigation options Code Issues Pull requests Actions Security and quality Insights n8n@2.37.7 Compare Choos
  • Release n8n@2.38.2 · n8n-io/n8n · GitHub →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026n8n-io / n8n Public Notifications You must be signed in to change notification settings Fork 60.9k Star 206k Code Issues 358 Pull requests 751 Actions Security and quality 196 Insights Additional navigation options Code Issues Pull requests Actions Security and quality Insights n8n@2.38.2 Pre-release P
  • Path Injection in Elasticsearch and ElasticSecurity Nodes via Unencoded Identifiers · Advisory · n8n-io/n8n · GitHub →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026n8n-io / n8n Public Notifications You must be signed in to change notification settings Fork 60.9k Star 206k Code Issues 358 Pull requests 751 Actions Security and quality 196 Insights Additional navigation options Code Issues Pull requests Actions Security and quality Insights Path Injection in Elastic
04

Evidence and provenance

Published 8 Sept 2026 · Last source change 9 Sept 2026, 15:13 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-09
European sourceENISA EUVD · EUVD-2026-74277
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added mitigation: github.com/GHSA-f2cp-m7mv-8jpv; added remediation: github.com/GHSA-f2cp-m7mv-8jpv.
    Before
    no authoritative guidance recorded
    After
    mitigation: github.com/GHSA-f2cp-m7mv-8jpv · remediation: github.com/GHSA-f2cp-m7mv-8jpv
    security-advisories@github.com ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 2.38.0, < 2.38.2; >= 2.0.0, < 2.37.7; < 1.123.76 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    n8n: >= 2.38.0, < 2.38.2, >= 2.0.0, < 2.37.7, < 1.123.76 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    security-advisories@github.com ↗
  4. ENISA EUVD mappingEUVD-2026-74277 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-74277"}
    ENISA EUVD ↗
  5. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Mitigation reference recorded
ENISA EUVD · EUVD-2026-74277↗CVE authority or vendor reference · GitHub GHSA-F2CP-M7MV-8JPV↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-86079 · cve.blacktree.nl