CVE-2026-65599

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. 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: epss, nvd
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 27, 2026

Advisory Details (2)

Auto-updated Jul 22, 2026
Patch 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-header
github 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-6qhm

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
n8n—2.29.8—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 41× 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.

  1. 2026-09-14 01:52 UTCEG score recompute
  2. 2026-09-13 01:25 UTCEG score recompute
  3. 2026-09-11 22:09 UTCEG score recompute
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 21:40 UTCEG score recompute
  7. 2026-09-09 09:18 UTCEG score recompute
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-07 21:43 UTCEG score recompute
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-05 19:35 UTCEG score recompute
  13. 2026-09-05 15:31 UTCEPSS rescore
  14. 2026-09-04 13:58 UTCEG score recompute
  15. 2026-09-04 05:07 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 23:41 UTCEG score recompute
  18. 2026-09-01 13:54 UTCEPSS rescore
  19. 2026-08-31 01:25 UTCEG score recompute
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-30 00:56 UTCEG score recompute
  23. 2026-08-28 21:42 UTCEPSS rescore
  24. 2026-08-27 11:10 UTCEG score recompute
  25. 2026-08-26 14:47 UTCEPSS rescore
Show 74 more
  1. 2026-08-26 10:43 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 09:18 UTCEG score recompute
  4. 2026-08-23 08:21 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 07:53 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 07:25 UTCEG score recompute
  9. 2026-08-20 22:56 UTCEPSS rescore
  10. 2026-08-20 06:57 UTCEG score recompute
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-19 06:30 UTCEG score recompute
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-18 05:36 UTCEG score recompute
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 04:53 UTCEG score recompute
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 04:26 UTCEG score recompute
  19. 2026-08-15 03:59 UTCEG score recompute
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 03:31 UTCEG score recompute
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 03:04 UTCEG score recompute
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-12 02:37 UTCEG score recompute
  26. 2026-08-11 02:10 UTCEG score recompute
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-10 01:43 UTCEG score recompute
  29. 2026-08-09 13:47 UTCEPSS rescore
  30. 2026-08-09 01:15 UTCEG score recompute
  31. 2026-08-08 16:37 UTCEPSS rescore
  32. 2026-08-08 00:48 UTCEG score recompute
  33. 2026-08-07 00:20 UTCEG score recompute
  34. 2026-08-06 13:47 UTCEPSS rescore
  35. 2026-08-05 23:52 UTCEG score recompute
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-05 19:17 UTCEPSS rescore
  38. 2026-08-04 23:25 UTCEG score recompute
  39. 2026-08-04 15:10 UTCEPSS rescore
  40. 2026-08-04 10:39 UTCEPSS rescore
  41. 2026-08-03 22:58 UTCEG score recompute
  42. 2026-08-03 10:36 UTCEPSS rescore
  43. 2026-08-02 22:31 UTCEG score recompute
  44. 2026-08-02 02:27 UTCEPSS rescore
  45. 2026-08-01 22:04 UTCEG score recompute
  46. 2026-08-01 04:16 UTCEPSS rescore
  47. 2026-07-30 21:09 UTCEG score recompute
  48. 2026-07-30 16:28 UTCEPSS rescore
  49. 2026-07-30 01:30 UTCEPSS rescore
  50. 2026-07-28 20:00 UTCEG score recompute
  51. 2026-07-28 15:37 UTCEPSS rescore
  52. 2026-07-27 19:33 UTCEG score recompute▲ 1.40
  53. 2026-07-27 19:27 UTCNVD updateCVSS v3 → 6.5
  54. 2026-07-27 14:14 UTCEPSS rescore
  55. 2026-07-27 03:58 UTCEG score recompute
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 14:54 UTCEPSS rescore
  58. 2026-07-26 03:29 UTCEG score recompute
  59. 2026-07-25 14:18 UTCEPSS rescore
  60. 2026-07-25 14:18 UTCEPSS rescore
  61. 2026-07-24 14:18 UTCEPSS rescore
  62. 2026-07-24 14:18 UTCEPSS rescore
  63. 2026-07-23 14:18 UTCEPSS rescore
  64. 2026-07-23 14:18 UTCEPSS rescore
  65. 2026-07-23 03:22 UTCEG score recompute
  66. 2026-07-22 22:06 UTCEG score recompute
  67. 2026-07-22 18:45 UTCEG score recompute
  68. 2026-07-22 17:54 UTCGHSA enrichment
  69. 2026-07-22 17:29 UTCGHSA enrichment
  70. 2026-07-22 17:20 UTCGHSA enrichment
  71. 2026-07-22 13:35 UTCEG score recompute
  72. 2026-07-22 13:35 UTCGHSA enrichment
  73. 2026-07-22 11:32 UTCEG score recompute
  74. 2026-07-22 11:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

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, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65599 actively exploited?
CVE-2026-65599 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.2% of all scored CVEs.
What is the CVSS score of CVE-2026-65599?
CVE-2026-65599 has a CVSS v3 base score of 6.5 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-65599

Explore →

Is Your Infrastructure Affected by CVE-2026-65599?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs