CVE-2026-59208

MEDIUMNVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under NVD CVSS v3. EPSS exploit probability: 0.3% (16th percentile of EPSS-scored CVEs). 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.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

n8n is an open source workflow automation platform. Prior to 2.27.4 and from 2.28.0 prior to 2.28.1, n8n instances configured with more than one trusted token-exchange issuer resolved external identities to local accounts using only the JWT sub claim and ignored the iss claim, allowing an attacker with a valid token from one trusted issuer and a sub matching a victim under another issuer to authenticate as that victim. This issue is fixed in versions 2.27.4 and 2.28.1.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100CISA SSVC

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
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 9, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jul 9, 2026
Patch available. Sources: github, github_release.
github_release Patch Available

[email protected]

Patch available: n8n-io/n8n [email protected] (pre-release)

https://github.com/n8n-io/n8n/releases/tag/n8n%402.28.1
github_release Patch Available

[email protected]

Patch available: n8n-io/n8n [email protected]

https://github.com/n8n-io/n8n/releases/tag/n8n%402.27.4
githubMentions a patch (unverified)

Cross-Issuer Token Exchange Account Binding via Subject-Only Identity Resolution · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-mq3m-f8x3-579w

Vendor Advisories for CVE-2026-59208(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 rangeFix by version rangeDependents
n8n—
  • 2.28.0 up to 2.28.1: fixed in 2.28.1
  • every version up to 2.27.4: fixed in 2.27.4
—

Weakness Classification(2)

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

Data Freshness Timeline

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

Showing the most recent 100 of 132 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-59208?
CVE-2026-59208 is a medium vulnerability published on July 9, 2026. n8n is an open source workflow automation platform. Prior to 2.27.4 and from 2.28.0 prior to 2.28.1, n8n instances configured with more than one trusted token-exchange issuer resolved external identities to local accounts using only the JWT sub claim and ignored the iss claim, allowing an attacker…
When was CVE-2026-59208 disclosed?
CVE-2026-59208 was first published on July 9, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59208 actively exploited?
CVE-2026-59208 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59208?
CVE-2026-59208 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-59208?
A fix for CVE-2026-59208 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59208 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59208?

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

Book a Demo →Browse All CVEs