CVE-2026-86079Network attack vector

Elasticsearch data exposure via unencoded REST identifiers

Published Sep 8, 2026 · Updated Sep 9, 2026

Path injection in n8n before 1.123.76, 2.0.0 through 2.37.6, and 2.38.0 through 2.38.1 lets remote authenticated users read Elasticsearch data. The Elasticsearch and ElasticSecurity nodes interpolate workflow-controlled index and document identifiers into REST paths without encoding each value as a single path segment, so separators or dot segments redirect the request. Workflow-edit access and a stored Elasticsearch credential are required; exploitation can expose data from another index or a cluster administration endpoint within that credential's permissions.

CVSS severity6.3
Medium
EPSS probability0.33%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Path injection in n8n before 1.123.76, 2.0.0 through 2.37.6, and 2.38.0 through 2.38.1 lets remote authenticated users read Elasticsearch data. The Elasticsearch and ElasticSecurity nodes interpolate workflow-controlled index and document identifiers into REST paths without encoding each value as a single path segment, so separators or dot segments redirect the request. Workflow-edit access and a stored Elasticsearch credential are required; exploitation can expose data from another index or a cluster administration endpoint within that credential's permissions.

The record

CVE
CVE-2026-86079
Published
Sep 8, 2026
Updated
Sep 9, 2026
Vendor
n8n
Product
n8n
Classifications
CWE-22
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 8, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 9, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.123.76
  2. Affected versionversion=>= 2.0.0, < 2.37.7
  3. Affected versionversion=>= 2.38.0, < 2.38.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

n8n · n8nversion=< 1.123.76; version=>= 2.0.0, < 2.37.7; version=>= 2.38.0, < 2.38.2

Published CVSS scores

6.3GitHub CNACVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo