n8n: Google Service Account Private Key Exposed in JWT Header
MediumCVE-2026-65599 · Published Jul 22, 2026
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | < 1.123.64 | 1.123.64 |
| >= 2.30.0, < 2.30.1 | 2.30.1 | |
| >= 2.0.0-rc.0, < 2.29.8 | 2.29.8 |
Details and references
## Impact When n8n was configured with a Google Service Account key, the full PEM private key was mistakenly placed in the JWT header's `kid` field (which should only have held a key identifier). Since JWT headers were Base64-encoded rather than encrypted, the key could be recovered by anything that logged or inspected the JWT. An attacker who obtained the key could impersonate the service account and access or modify any Google Cloud resource it was authorized to use. Only instances using Google Service Account credentials are affected. ## Patches The issue has been fixed in n8n versions 1.123.64, 2.29.8, and 2.30.1. Users should upgrade to one of these versions or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Avoid using Google Service Account credentials until the instance is patched. - Rotate any Google Service Account keys that may have been used with an affected n8n version. - Review proxy, load balancer, and application logs for JWT headers that may contain exposed key material and treat any such keys as compromised. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
- CVSS 4.0
- CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:L
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-312
- Also known as
- CVE-2026-65599
- github.com/n8n-io/n8n/security/advisories/GHSA-9r8p-h6cc-6qhm
- nvd.nist.gov/vuln/detail/CVE-2026-65599
- github.com/n8n-io/n8n
- github.com/n8n-io/n8n/releases/tag/n8n@1.123.64
- github.com/n8n-io/n8n/releases/tag/n8n@2.29.8
- github.com/n8n-io/n8n/releases/tag/n8n@2.30.1
- www.vulncheck.com/advisories/n8n-before-credential-exposure-via-jwt-header
More n8n advisories
All n8n| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Jul 22 | n8n: AI Agents Project Viewer Privilege Escalation via run_node_tool CVE-2026-65015Highfixed in 2.29.8, 2.30.1 | High | 2.29.8, 2.30.1 |
| Jul 22 | n8n: Race Condition in Git Clone Node Allows Authenticated Users to Achieve Remote Code Execution CVE-2026-65598Highfixed in 1.123.64, 2.29.8, 2.30.1 | High | 1.123.64, 2.29.8, 2.30.1 |
| Jul 22 | n8n: DOM-Based XSS via Unsandboxed iframe srcdoc in HTML Preview CVE-2026-65597Highfixed in 1.123.64, 2.29.8, 2.30.1 | High | 1.123.64, 2.29.8, 2.30.1 |
| Jul 22 | n8n: Stored DOM XSS via Resource Locator `cachedResultUrl` CVE-2026-65592Highfixed in 1.123.64, 2.29.8, 2.30.1 | High | 1.123.64, 2.29.8, 2.30.1 |
| Jul 22 | n8n: Shared Credential Header Leak via HTTP Request Pagination Expression CVE-2026-59209Highfixed in 1.123.61, 2.27.4, 2.28.1 | High | 1.123.61, 2.27.4, 2.28.1 |
| Jul 22 | n8n: Prototype Pollution via Workflow Credentials Leads to Unauthenticated User and Project Enumeration CVE-2026-59206Highfixed in 1.123.61, 2.27.4, 2.28.1 | High | 1.123.61, 2.27.4, 2.28.1 |