Quick answers
- Is CVE-2026-86074 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86074 being exploited in the wild.
- How severe is CVE-2026-86074?
- High severity, with a CVSS score of 7.1, published 8 September 2026.
- Which products and versions are affected?
- N8n >= 2.38.0, < 2.38.2; < 2.37.7; n8n (npm) SEMVER:introduced=2.38.0,fixed=2.38.2.
- Is there a fix for CVE-2026-86074?
- Yes. n8n (npm): upgrade to 2.38.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86074 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-86074?
- 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 2.38.2 or later
npm install n8n@2.38.2
Technical details
This is a server-side request forgery (SSRF) vulnerability in n8n's Instance AI credential setup flow. The vulnerable component failed to validate that credential test/verification probe URLs matched the workflow node's origin before making authenticated requests or following redirects. An attacker could inject an arbitrary URL into the credential setup flow, causing the n8n server to send authenticated requests to a malicious destination, potentially exfiltrating third-party API credentials or other sensitive data. The attack requires user interaction (an authenticated user must manually inject the attacker URL into the setup flow). The fix derives the credential destination from the node's own URL and restricts all authenticated requests, redirects, and probes to that origin.
Affected products
- n8n n8n >= 2.38.0, < 2.38.2; < 2.37.7
Identifiers
- CVE-2026-86074
- GHSA-q5wm-mgqx-fv2f
Timeline
- 2026-09-02: disclosed
- 2026-09-02: patched: Fixes released in n8n 2.38.2 and 2.37.7