{"items":[{"id":"NVI-00013912","kind":"vulnerability","title":"n8n: Path Injection in Elasticsearch and ElasticSecurity Nodes via Unencoded Identifiers","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-f2cp-m7mv-8jpv","CVE-2026-86079"],"plain_summary":"GitHub lists this reviewed advisory for n8n, n8n, n8n. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1bff3ba4f419bc7ada8c3b463f31ff28"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-1bff3ba4f419bc7ada8c3b463f31ff28","url":"https://github.com/advisories/GHSA-f2cp-m7mv-8jpv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-f2cp-m7mv-8jpv","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T22:54:05.264Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1bff3ba4f419bc7ada8c3b463f31ff28"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\n\nThe Elasticsearch and ElasticSecurity nodes built REST endpoints by interpolating user-provided identifiers straight into the request path. A value containing path separators or dot segments changed which endpoint the request actually reached, so an operation intended for one document could hit another index or a cluster administration endpoint instead, under the stored Elasticsearch credential. The patch encodes each identifier as a single URL path segment and rejects values that normalise away.\n\n## Patches\n\nThe issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Disable the affected nodes by adding `n8n-nodes-base.elasticsearch` and `n8n-nodes-base.elasticSecurity` to the `NODES_EXCLUDE` environment variable if they are not required.\n- Audit existing workflows that use these nodes and ensure that index and document identifier fields do not accept externally-controlled input.\n\nThese w","public_affected_ranges":["< 1.123.76"]},{"certainty":"source_listed","source_ids":["sr-1bff3ba4f419bc7ada8c3b463f31ff28"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\n\nThe Elasticsearch and ElasticSecurity nodes built REST endpoints by interpolating user-provided identifiers straight into the request path. A value containing path separators or dot segments changed which endpoint the request actually reached, so an operation intended for one document could hit another index or a cluster administration endpoint instead, under the stored Elasticsearch credential. The patch encodes each identifier as a single URL path segment and rejects values that normalise away.\n\n## Patches\n\nThe issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Disable the affected nodes by adding `n8n-nodes-base.elasticsearch` and `n8n-nodes-base.elasticSecurity` to the `NODES_EXCLUDE` environment variable if they are not required.\n- Audit existing workflows that use these nodes and ensure that index and document identifier fields do not accept externally-controlled input.\n\nThese w","public_affected_ranges":[">= 2.38.0, < 2.38.2"]},{"certainty":"source_listed","source_ids":["sr-1bff3ba4f419bc7ada8c3b463f31ff28"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\n\nThe Elasticsearch and ElasticSecurity nodes built REST endpoints by interpolating user-provided identifiers straight into the request path. A value containing path separators or dot segments changed which endpoint the request actually reached, so an operation intended for one document could hit another index or a cluster administration endpoint instead, under the stored Elasticsearch credential. The patch encodes each identifier as a single URL path segment and rejects values that normalise away.\n\n## Patches\n\nThe issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Disable the affected nodes by adding `n8n-nodes-base.elasticsearch` and `n8n-nodes-base.elasticSecurity` to the `NODES_EXCLUDE` environment variable if they are not required.\n- Audit existing workflows that use these nodes and ensure that index and document identifier fields do not accept externally-controlled input.\n\nThese w","public_affected_ranges":[">= 2.0.0, < 2.37.7"]}],"null_published_at":"2026-11-02T10:00:37.173Z","source_updated_at":"2026-09-10T21:05:45.000Z","source_disclosed_at":"2026-09-10T21:05:43.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T22:54:05.264Z"}],"next_cursor":null,"snapshot_revision":"42594"}