CVE-2026-65599

The record

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.

Affected packages

Related vulnerabilities

• CVE-2026-86280 A vulnerability was identified in SourceCodester Syllabus-Aligned Learning Management &… CWE-312
• CVE-2026-53603 nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. CWE-312
• CVE-2026-73748 A vulnerability in the affected interface of HPE Networking Fabric Composer allows an… CWE-312
• CVE-2026-83551 Cleartext storage of sensitive information in the @step and @remote decorator pipeline… CWE-312
• CVE-2026-77975 The affected Ebyte product exports administrative credentials and other sensitive… CWE-312
• CVE-2026-82699 A flaw has been found in sambitraj Student Management System up to… CWE-312
• CVE-2026-82640 browser-use web-ui versions 2.0.0 through 3.0.0 write configured LLM API keys to disk in… CWE-312
• CVE-2026-77970 Cleartext Storage of Sensitive Information vulnerability in ash-project ash_paper_trail… CWE-312