n8n: Google Service Account Private Key Exposed in JWT Header
CVE-2026-65599 · GHSA-9r8p-h6cc-6qhm · published 2026-07-22
- Severity
- Medium
- CVSS score
- 5.1
- Chance of exploitation (EPSS)
- 0.25%
- Fixed in
- 2.30.1
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
When n8n was configured with a Google Service Account key, the full PEM private key was mistakenly placed in the JWT header's kid field (which should only have held a key identifier). Since JWT headers were Base64-encoded rather than encrypted, the 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.
Upgrade n8n to 2.30.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The issue has been fixed in n8n versions 1.123.64, 2.29.8, and 2.30.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Avoid using Google Service Account credentials until the instance is patched. Rotate any Google Service Account keys that may have been used with an affected n8n version. Review proxy, load balancer, and application logs for JWT headers that may contain exposed key material and treat any such keys as compromised. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- HighWorkspace dotenv files could override provider credentialsopenclaw
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.