mediumCVSS 6.5NVD status: Analyzed

CVE-2026-65599

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 f...

Componentn8n
Severitymedium (CVSS 6.5)
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Published (NVD)2026-07-22
Last modified2026-07-27
Affected versions
n8n < 1.123.64
n8n < 1.123.64
n8n >= 2.0.0, < 2.29.8
n8n >= 2.0.0, < 2.29.8
n8n = 2.30.0
n8n = 2.30.0
Fixed in1.123.64, 2.29.8
WeaknessCWE-312
CISA KEVnot listed

NVD description

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.

Does CVE-2026-65599 hit the version you run?Paste your docker-compose.yml, requirements.txt or package.json. The scanner checks your pinned versions against this CVE and every other one we track for n8n.
Check my stack

What to do

  • Upgrade n8n to 1.123.64 or later (or the patched release of your branch: 2.29.8).
  • Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

Read more

Other n8n CVEs

All n8n CVEs