Quick answers
- Is CVE-2026-65596 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65596 being exploited in the wild.
- How severe is CVE-2026-65596?
- 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 < 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-65596?
- 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-65596 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-65596?
- 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
An incorrect authorization vulnerability (CWE-863) exists in n8n where the GraphQL node does not enforce the 'Allowed HTTP Request Domains' restriction. While the standard HTTP Request node respects these boundaries, the GraphQL node allows HTTP-based credentials (including Basic Auth, Header Auth, and OAuth) to be sent to any arbitrary domain. An authenticated attacker with workflow creation or editing privileges can configure a GraphQL node to point to a malicious endpoint, thereby exfiltrating shared credentials. The vulnerability is patched in versions 1.123.64, 2.29.8, and 2.30.1.
Affected products
- n8n-io n8n < 1.123.64, >= 2.0.0 < 2.29.8, >= 2.30.0 < 2.30.1
Identifiers
- CVE-2026-65596
- GHSA-gq66-9cw5-j5jm
Timeline
- 2026-07-08: disclosed
- 2026-07-22: advisory