Quick answers
- Is CVE-2026-65599 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65599 being exploited in the wild.
- How severe is CVE-2026-65599?
- 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-65599?
- 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-65599 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-65599?
- 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 vulnerability in n8n's handling of Google Service Account credentials resulted in the full PEM private key being placed in the 'kid' (Key ID) field of JWT headers. Because JWT headers are Base64-encoded rather than encrypted, the private key is effectively stored in cleartext. An attacker with access to application logs, proxy logs, or network traffic containing these JWTs could extract the key to impersonate the service account. This issue affects n8n instances configured with Google Service Account credentials across several version ranges. 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-65599
- GHSA-9r8p-h6cc-6qhm
Timeline
- 2026-07-08: disclosed: Initial report to n8n-io/n8n
- 2026-07-22: advisory: GitHub Advisory published