CVE-2026-77069
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
Summary
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 Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| n8n-io | n8n | 0 < 1.123.69 | affected |
| n8n-io | n8n | 1.123.69 | unaffected |
| n8n-io | n8n | 0 < 2.34.1 | affected |
| n8n-io | n8n | 2.34.1 | unaffected |
| n8n-io | n8n | 0 < 2.33.4 | affected |
| n8n-io | n8n | 2.33.4 | unaffected |
Weaknesses
- CWE-918: Server-Side Request Forgery (SSRF)
ADP Enrichment
CISA ADP Vulnrichment
- SSVC:
- Exploitation: none
- Automatable: no
- Technical Impact: partial
References
- https://github.com/n8n-io/n8n/security/advisories/GHSA-c4f6-59xq-95ww
- https://www.vulncheck.com/advisories/n8n-before-ssrf-protection-bypass-via-oauth2
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.