CVE-2026-65599
n8n before 1.123.64, 2.29.8, and 2.30.1 Credential Exposure via JWT Header
- State
- Published
- Severity
- 5.1 Medium
- Published
- Jul 22, 2026
- Updated
- Oct 29, 2026
- Reserved
- Jul 22, 2026
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 4.0 | 5.1 Medium | 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 | VulnCheck |
Weaknesses
- CWE-312 Cleartext Storage of Sensitive Information
Affected Products
| Product | Versions |
|---|---|
n8nn8n-io |
|
n8nn8n-io |
|
n8nn8n-io |
|
References
- GitHub Security Advisory (GHSA-9r8p-h6cc-6qhm)vendor-advisory
- VulnCheck Advisory: n8n before 1.123.64 Credential Exposure via JWT Headerthird-party-advisory
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.