BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

CVE-2026-65599

5.1 medium SSVC exploitation: none Analyzed
NVD · CVE.org

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.

Fix

Patch, vendor advisory and mitigation references on NVD 1

Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.

Change history 1

  1. First seenCVSS 5.1 · n8nNVD modified 2026-10-24 17:10

Affected (CPE criteria) 4

  • cpe:2.3:a:n8n:n8n:*:*:*:*:community:node.js:*:*
  • cpe:2.3:a:n8n:n8n:*:*:*:*:enterprise:node.js:*:*
  • cpe:2.3:a:n8n:n8n:2.30.0:*:*:*:community:node.js:*:*
  • cpe:2.3:a:n8n:n8n:2.30.0:*:*:*:enterprise:node.js:*:*

References 2