| Package | Affected versions | Patched versions |
|---|---|---|
| n8n | ≥ 2.0.0, < 2.37.7≥ 2.38.0, < 2.38.2< 1.123.76 | 2.37.72.38.21.123.76 |
| n8n | ≥ 2.0.0, < 2.37.7≥ 2.38.0, < 2.38.2< 1.123.76 | 2.37.72.38.21.123.76 |
The 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.
The 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.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
n8n-nodes-base.elasticsearch and n8n-nodes-base.elasticSecurity to the NODES_EXCLUDE environment variable if they are not required.These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free