| Package | Affected versions | Patched versions |
|---|---|---|
| n8n | = 2.30.0≥ 2.0.0, < 2.29.8< 1.123.64 | 2.29.81.123.64 |
| n8n | ≥ 2.0.0-rc.0, < 2.29.8≥ 2.30.0, < 2.30.1< 1.123.64 | 2.29.82.30.11.123.64 |
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.
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:
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free