All vulnerabilities

Servers and applications

GHSA-c772-hjfp-gfc2

Integration Nodes Send Authenticated Requests to Unintended API Endpoints

Severity
Medium 5.3
Published
13 Nov 2026
Last changed
13 Nov 2026
Added to UpHeron
13 Nov 2026
Fixed in
1.123.96, 2.47.6, 2.48.3, 3.2.2
Attack
Over the network · Only under certain conditions · Needs a user account · No user action needed
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
Sources
Project advisories (GitHub)

Description

Multiple n8n nodes built the URL path of their API requests from node parameters such as record, table or resource IDs. These values were not encoded, so a value containing relative path segments could change which endpoint of the same service the request reached. Where a workflow passed untrusted input, such as a webhook body, into one of these parameters, a caller could make the node read, modify or delete resources outside the workflow's intended scope, with the privileges of the node's stored credential.

From n8n-io/n8n's security advisory.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

  • Restrict n8n instance access to fully trusted users only.
  • Audit active workflows and ensure that node parameters holding record, table or resource IDs do not incorporate untrusted external data via expressions.
  • Apply network-level controls to restrict access to webhook endpoints that feed into these workflows.
  • Limit the permissions of the credentials used by affected workflows to the resources those workflows need.
  • Deactivate affected workflows until the instance is patched.
Workarounds as given by n8n-io/n8n's security advisory.

Affected software

SoftwareAffected versions
n8nServers and applications · github:n8n-io/n8n
  • Every version before 1.123.96
  • Every version before 3.2.2
  • Every version before 2.48.3
  • Every version before 2.47.6

References