CVE-2026-45707

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% 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:github_m, epss
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

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

n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. Prior to 2.51.2, when ENABLE_MULTI_TENANT=true, the HTTP transport documents that the target n8n instance is selected per-request from x-n8n-url / x-n8n-key headers. Requests that omitted those headers — or supplied only one of them — silently fell back to the process-level N8N_API_URL / N8N_API_KEY credentials configured for the operator's own n8n instance. As a result, an authenticated MCP tenant could cause n8n management calls to execute against the operator's instance instead of its own. This affects HTTP-mode deployments of n8n-mcp that are run as a shared multi-tenant service. Single-tenant deployments (ENABLE_MULTI_TENANT unset or false) are not affected. This vulnerability is fixed in 2.51.2.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
14.5%
KEV
Not listed

Published

May 18, 2026

Last Modified

June 1, 2026

Advisory Details (3)

Auto-updated Jun 3, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

Release v2.51.2

Patch available: czlonkowski/n8n-mcp v2.51.2

https://github.com/czlonkowski/n8n-mcp/releases/tag/v2.51.2
github_commit Patch Available

commit 853015d0897b (czlonkowski/n8n-mcp)

Patch available: czlonkowski/n8n-mcp v2.51.2 (contains commit 853015d0897b)

https://github.com/czlonkowski/n8n-mcp/commit/853015d0897be7cf2d9d4726de195c938e4395ab
github Patch Available

Multi-tenant MCP requests fall back to process-level n8n credentials when tenant headers are absent or incomplete · Advisory · czlonkowski/n8n-mcp · GitHub

https://github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-jxx9-px88-pj69

Vendor Advisories for CVE-2026-45707(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-mcp—2.51.2—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45707?
CVE-2026-45707 is a high vulnerability published on May 18, 2026. n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. Prior to 2.51.2, when ENABLEMULTITENANT=true, the HTTP transport documents that the target n8n instance is selected per-request from x-n8n-url / x-n8n-key headers. Requests that…
When was CVE-2026-45707 disclosed?
CVE-2026-45707 was first published in the National Vulnerability Database on May 18, 2026, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45707 actively exploited?
CVE-2026-45707 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45707?
CVE-2026-45707 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-45707?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45707, 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-45707

Explore →

Is Your Infrastructure Affected by CVE-2026-45707?

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

Start Free Scan →Browse All CVEs