Vulnerability in N8n
CVE-2026-65599
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.
EPSS: 0.002 (4.8th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
Affected products
- N8n — versions 2.30.0
- N8n-io N8n — versions 0, 1.123.64, 2.30.1
Weakness classification (CWE)
References
- disclosure@vulncheck.com (vendor-advisory, Mitigation, Vendor Advisory)
- disclosure@vulncheck.com (Third Party Advisory, third-party-advisory)
Frequently asked questions
- What is CVE-2026-65599?
- CVE-2026-65599 is a medium-severity vulnerability in N8n, classified under Cleartext Storage of Sensitive Information. CVSS score: 6.5/10. Published 2026-07-22.
- How severe is CVE-2026-65599?
- Medium severity. CVSS v3 base score is 6.5 out of 10.