CVE-2026-65599

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% 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: cna:vulncheck, epss
Trending — 4 sources updated this week
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.1Exploit: 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
5.1
EG Score
5.1(medium)
EG Risk
23(Track)
EG Risk 23/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
Severity51% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 24, 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 20× in last 7d / 20× 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-07-27 03:58 UTCEG score recompute
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 03:29 UTCEG score recompute
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:22 UTCEG score recompute
  12. 2026-07-22 22:06 UTCEG score recompute
  13. 2026-07-22 18:45 UTCEG score recompute
  14. 2026-07-22 17:54 UTCGHSA enrichment
  15. 2026-07-22 17:29 UTCGHSA enrichment
  16. 2026-07-22 17:20 UTCGHSA enrichment
  17. 2026-07-22 13:35 UTCEG score recompute
  18. 2026-07-22 13:35 UTCGHSA enrichment
  19. 2026-07-22 11:32 UTCEG score recompute
  20. 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 24, 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 93.7% of all scored CVEs.
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).
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