Server-side Request Forgery (SSRF) Affecting n8n-nodes-base package, versions <2.34.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-N8NNODESBASE-20054036
- published23 Sept 2026
- disclosed20 Aug 2026
- creditPr0ph3t3
Introduced: 20 Aug 2026
CVE-2026-77069 (opens in a new tab)How to fix?
Upgrade n8n-nodes-base to version 2.34.1 or higher.
Overview
n8n-nodes-base is a Base nodes of n8n
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the OAuth2 authorization-code-to-access-token exchange, which issues its request through a separate HTTP client that lacks the SSRF guard applied to the discovery and dynamic-client-registration requests. A user able to create credentials can make the instance send token-exchange POST requests to internal addresses and read the reflected response body, by pointing a credential's access-token URL at an internal target and completing the OAuth2 flow. The request method, headers, and body are fixed beyond the OAuth2 fields, so disclosure is bounded to targets that respond usefully to that particular request shape.