CVE-2026-77069: n8n · Server-Side Request Forgery (SSRF)
Affects n8nSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 1.123.69 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.123.69, 2.34.1, 2.33.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| n8n-ion8n | Affected
| Fixed in
|
| n8n-ion8n | Affected
| Fixed in
|
| n8n-ion8n | Affected
| Fixed in
|
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability is fixed in n8n versions 1.123.69, 2.33.4, and 2.34.1. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated or required beyond applying the official patches.
Description
CVE-2026-77069 is a Server-Side Request Forgery (SSRF) vulnerability in n8n before versions 1.123.69, 2.33.4, and 2.34.1. It occurs in the OAuth2 credential authorization-code-to-access-token exchange, where a separate HTTP client without SSRF protection is used. An attacker with credential-creation permissions can exploit this to send POST requests to internal addresses and receive reflected responses limited to the token exchange request's output.