n8n
Affected
- introduced
0, fixed1.123.64(semver)
Fixed versions
1.123.64
Fix
- Fixed version
1.123.64npm install [email protected]
Advisory
Also known as: CVE-2026-65599
n8n: Google Service Account Private Key Exposed in JWT Header
Impact
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.
Patches
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.
Workarounds
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.
Medium Basis: The source's own band: MODERATE
0, fixed 1.123.64 (semver)1.123.64
1.123.64npm install [email protected]2.30.0, fixed 2.30.1 (semver)2.30.1
2.30.1npm install [email protected]2.0.0-rc.0, fixed 2.29.8 (semver)2.29.8
2.29.8npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0