SSRF in N8n
CVE-2026-77069
- CVSS v3
- 4.3 Medium
- Public exploits
- None known
- EPSS
- 0.003 · 22.4th percentile
- Published
- 2026-08-20
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).
Vulnerability class: SSRF (Server-Side Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- Low
PR:L - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- Low
C:L - Integrity
- None
I:N - Availability
- None
A:N
EPSS exploit prediction
EPSS 0.003, 22.4th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- N8n — versions 2.34.0
- N8n-Io N8n
Weakness classification (CWE)
References
- GitHub Security Advisory (GHSA-c4f6-59xq-95ww) (vendor-advisory, Mitigation, Vendor Advisory)
- VulnCheck Advisory: n8n before 1.123.69 SSRF Protection Bypass via OAuth2 (Third Party Advisory, third-party-advisory)