CVE-2026-65599: n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a credential exposure vulnerability: when configured
CVE-2026-65599 is a medium-severity flaw (CVSS 6.5) affecting n8n. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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 imperson
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 85%) |
| CISA exploited list | No |
| Weakness | CWE-312 |
| Published | 2026-07-22 |
| Last modified | 2026-10-24 |
Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-65599?
n8n: upgrade to 1.123.64, 2.29.8. Exact commands for each OS are on this page.
Is CVE-2026-65599 being exploited?
CVE-2026-65599 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-65599 affect?
CVE-2026-65599 affects n8n. Severity is medium (CVSS 6.5). 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
How urgent is CVE-2026-65599?
Priority 27/100. No elevated risk signals yet.
Related CVEs
- CVE-2026-65590 CRITICAL 9.8 UPGRADE n8n before 2.29.8 and 2.30.x before 2.30.1 does not enforce shell sandbox restrictions on Linux and Windows in
- CVE-2026-65591 HIGH 8.8 UPGRADE n8n contains a sanitizer bypass vulnerability in the legacy expression evaluator's computed-member handler
- CVE-2026-65595 HIGH 8.8 UPGRADE n8n before 2.30.1 and 2.29.8 assigns all Public API key scopes to JWTs issued through the Token Exchange modul
- CVE-2026-65015 HIGH 8.8 UPGRADE n8n versions before 2.30.1 contain a privilege escalation vulnerability in the AI Agents feature where the nod
- CVE-2026-65016 HIGH 8.8 UPGRADE n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a privilege escalation vulnerability in Enterprise SS