CyberRota Analysis
AI-GeneratedThe vulnerability affects n8n versions prior to 1.123.69, 2.33.4, and 2.34.1, allowing users with credential-creation permissions to bypass SSRF protections during the OAuth2 token exchange process. This can lead to unauthorized access to internal services, as an attacker can manipulate the access-token URL to exfiltrate data from internal endpoints. Organizations using n8n should prioritize patching to mitigate potential data exposure risks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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).
Related CVEs
Other vulnerabilities affecting the same vendor(s)