GHSA-q5wm-mgqx-fv2f: SSRF
Impact
Instance AI credential setup accepted a credential test/verification URL without checking it matched the workflow node's origin. Exfiltration required the user to actively inject an attacker-controlled URL into the setup flow. The patch derives the credential destination from the node's own URL and confines authenticated requests, redirects and probes to that origin.
Patches
The issue has been fixed in n8n versions 2.38.2 and 2.37.7. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Disable the Instance AI module by removing instance-ai from the N8NENABLEDMODULES environment variable if it is not required. - Restrict n8n instance access to fully trusted users only. - Rotate any third-party API credentials that were set up using the Instance AI credential-setup flow on affected versions.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.37.7 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.38.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.38.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.37.7 - Configuration
If Instance AI is not required, disable it by removing `instance-ai` from the `N8N_ENABLED_MODULES` environment variable.
n8n Instance AI module N8N_ENABLED_MODULES = remove instance-ai - Compensating control
Restrict access to the n8n instance to fully trusted users only.
- Operational
Rotate any third-party API credentials that were set up using the Instance AI credential-setup flow on affected versions.
Event History
Frequently Asked Questions
What conditions are required for exploitation?
An attacker must cause a user to actively provide an attacker-controlled credential test or verification URL during the Instance AI credential-setup flow. The issue is therefore most relevant where untrusted users can access or influence that setup process.
Which versions contain the fix?
Upgrade n8n to version 2.38.2, 2.37.7, or a later version. The patch derives the credential destination from the workflow node's URL and limits authenticated requests, redirects, and probes to that origin.
What can administrators do before upgrading?
If Instance AI is not needed, remove instance-ai from the N8N_ENABLED_MODULES environment variable to disable it. Also restrict access to fully trusted users and rotate third-party API credentials configured through the Instance AI credential-setup flow on affected versions; these are temporary mitigations only.