Vulnerability Description
n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a credential exposure vulnerability: when configured with a Google Service Account key, the full PEM private key was mistakenly placed in the JWT header's kid field (intended only for a key identifier). Because JWT headers are Base64-encoded rather than encrypted, the private 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| N8N | N8N | < 1.123.64 |
Related Weaknesses (CWE)
References
- https://github.com/n8n-io/n8n/security/advisories/GHSA-9r8p-h6cc-6qhmMitigationVendor Advisory
- https://www.vulncheck.com/advisories/n8n-before-credential-exposure-via-jwt-headThird Party Advisory
FAQ
What is CVE-2026-65599?
CVE-2026-65599 is a vulnerability with a CVSS score of 6.5 (MEDIUM). n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a credential exposure vulnerability: when configured with a Google Service Account key, the full PEM private key was mistakenly placed in the J...
How severe is CVE-2026-65599?
CVE-2026-65599 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-65599?
Check the references section above for vendor advisories and patch information. Affected products include: N8N N8N.