n8n before 1.123.69 SSRF Protection Bypass via OAuth2
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.123.69, 2.33.4 and 2.34.1.
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).
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| n8n-io | <1.123.69, >=2.0.0 <2.33.4, >=2.34.0 <2.34.1 | 1.123.69, 2.33.4, 2.34.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket