n8n before 1.123.64, 2.29.8, and 2.30.1 Credential Exposure via JWT Header
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.123.64, 2.29.8 and 2.30.1.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| n8n-io | <1.123.64, >=2.0.0-rc.0 <2.29.8, >=2.30.0 <2.30.1 | 1.123.64, 2.29.8, 2.30.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket