CVE-2026-65599 json
n8n before 1.123.64, 2.29.8, and 2.30.1 Credential Exposure via JWT Header
published 3mo ago modified 13d ago also GHSA-9r8p-h6cc-6qhm , EUVD-2026-47643
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm n8n 1.123.64, 2.29.8, 2.30.1
- n8n-io n8n 1.123.64, 2.29.8, 2.30.1
Is CVE-2026-65599 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:L |
| CNA | 4.0 | 5.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | n8n | <1.123.64 >=2.30.0, <2.30.1 >=2.0.0-rc.0, <2.29.8 |
1.123.64 2.30.1 2.29.8 |
Affected products
- n8n-io n8n
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
-
github.com
/n8n-io/n8n/security/advisories/GHSA-9r8p-h6cc-6qhm
vendor-advisory, web, mitigation
-
vulncheck.com
/advisories/n8n-before-credential-exposure-via-jwt-header
third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-65599
advisory
-
github.com
/n8n-io/n8n
package
-
github.com
/n8n-io/n8n/releases/tag/n8n@1.123.64
web
-
github.com
/n8n-io/n8n/releases/tag/n8n@2.29.8
web
-
github.com
/n8n-io/n8n/releases/tag/n8n@2.30.1
web
Sources
- CVE List CVE-2026-65599
- GitHub Advisory GHSA-9r8p-h6cc-6qhm
- NVD CVE-2026-65599
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.