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.
CVE-2026-65599
MEDIUMPre-NVD 5.15.1Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 5.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: cna:vulncheck
5.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: —CVSS: 5.1Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.1
- EG Score
- 5.1(low)
- EPSS
- —
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 22, 2026Patch available. Sources: github.
generic
n8n before 1.123.64 Credential Exposure via JWT Header | Advisories | VulnCheck
https://www.vulncheck.com/advisories/n8n-before-credential-exposure-via-jwt-headergithub Patch Available
Google Service Account Private Key Exposed in JWT Header · Advisory · n8n-io/n8n · GitHub
https://github.com/n8n-io/n8n/security/advisories/GHSA-9r8p-h6cc-6qhmVendor Advisories for CVE-2026-65599(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 18:45 UTCEG score recompute
- 2026-07-22 17:54 UTCGHSA enrichment
- 2026-07-22 17:29 UTCGHSA enrichment
- 2026-07-22 17:20 UTCGHSA enrichment
- 2026-07-22 13:35 UTCEG score recompute
- 2026-07-22 13:35 UTCGHSA enrichment
- 2026-07-22 11:32 UTCEG score recompute
- 2026-07-22 11:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-312
Frequently asked(4)
What is CVE-2026-65599?
CVE-2026-65599 is a medium vulnerability published on July 22, 2026. 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…
When was CVE-2026-65599 disclosed?
CVE-2026-65599 was first published in the National Vulnerability Database on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-65599?
CVE-2026-65599 has a CVSS v4.0 base score of 5.1 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-65599?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65599, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65599
Is Your Infrastructure Affected by CVE-2026-65599?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.