n8n before 1.123.69 SSRF Protection Bypass via OAuth2
n8n-io n8n
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n-io n8n
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n before 1.123.69, 2.33.4, and 2.34.1 contains an SSRF protection bypass in the OAuth2 credential authorization-code-to-access-token exchange. While OAuth2 discovery and dynamic-client-registration requests use n8n's SSRF-protected HTTP client, the token exchange uses a separate client with no SSRF guard. A user with credential-creation permissions can set the access-token URL to an internal address and complete the OAuth2 flow, causing n8n to send a fixed-shape token-exchange POST to that target and reflect its response body back to the attacker (limited to what the target returns to this specific request).
From the CVE record · VulnCheck
The OAuth2 authorization-code-to-access-token exchange in n8n uses an HTTP client without SSRF protection. A user with credential-creation permissions who completes the OAuth2 flow can set the access-token URL to an internal address, causing n8n to send a fixed-shape POST and return the target's response body to that user.
Teams running n8n versions before 1.123.69, 2.33.4, or 2.34.1 should check their deployments.