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).
References
| Link | Resource |
|---|---|
| https://github.com/n8n-io/n8n/security/advisories/GHSA-c4f6-59xq-95ww | Mitigation Vendor Advisory |
| https://www.vulncheck.com/advisories/n8n-before-ssrf-protection-bypass-via-oauth2 | Third Party Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-08-20 12:16
Updated : 2026-09-01 20:01
NVD link : CVE-2026-77069
Mitre link : CVE-2026-77069
CVE.ORG link : CVE-2026-77069
JSON object : View
Products Affected
n8n
- n8n
CWE
CWE-918
Server-Side Request Forgery (SSRF)
