Quick answers
- Is CVE-2026-65593 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65593 being exploited in the wild.
- How severe is CVE-2026-65593?
- Medium severity, with a CVSS score of 4, published 22 July 2026.
- Which products and versions are affected?
- N8n < 1.123.64, < 2.29.8, < 2.30.1, < 1.123.64, >= 2.0.0-rc.0, < 2.29.8, >= 2.30.0, < 2.30.1; n8n (npm) SEMVER:introduced=0,fixed=1.123.64.
- Is there a fix for CVE-2026-65593?
- Yes. n8n (npm): upgrade to 1.123.64 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-65593 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-65593?
- Check whether you run N8n or n8n (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- n8n (npm): upgrade to 1.123.64 or later
npm install n8n@1.123.64
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in n8n's dynamic node parameters endpoints. The root cause is a lack of authorization scopes in the '/rest/dynamic-node-parameters/' endpoints, combined with the ability to override a node's 'baseURL' by providing an absolute URL in the routing configuration. An authenticated attacker, regardless of their permissions to create or execute workflows, can exploit this to make the server issue HTTP requests to arbitrary internal targets. The risk is heightened because SSRF protection is disabled by default in many configurations. Patches are available in versions 1.123.64, 2.29.8, and 2.30.1.
Affected products
- n8n-io n8n < 1.123.64, >= 2.0.0-rc.0, < 2.29.8, >= 2.30.0, < 2.30.1
Identifiers
- CVE-2026-65593
- GHSA-9w78-79q7-r4fp
Timeline
- 2026-07-08: disclosed: Initial disclosure by reporter
- 2026-07-22: advisory: GitHub Advisory published