CVE-2026-56778

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreMEDIUM confidence

Score 6.4 from GitHub Security Advisory published 2026-07-08. a secondary CVSS source baseline 6.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.4Exploit: None knownExposed: 0

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

n8n before 2.25.7 and 2.26.x before 2.26.2 contains an authorization bypass in the Public API execution retry endpoint, which authorizes access using the workflow:read scope instead of workflow:execute. An authenticated user with read-only access to a shared workflow can use the Public API to retry executions of that workflow, bypassing the intended permission boundary between read and execute access. This affects instances where workflows are shared with other users or across projects.

CVSS v3
6.4
EG Score
6.4(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
Severity64% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
Patch available. Sources: github.
generic

n8n - Authorization Bypass in Public API Execution Retry Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/n8n-authorization-bypass-in-public-api-execution-retry-endpoint
github Patch Available

Public API Execution Retry Authorization Bypass · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-h3jj-5f3v-3685

Vendor Advisories for CVE-2026-56778(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.25.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 75× 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 127 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56778?
CVE-2026-56778 is a medium vulnerability published on July 8, 2026. n8n before 2.25.7 and 2.26.x before 2.26.2 contains an authorization bypass in the Public API execution retry endpoint, which authorizes access using the workflow:read scope instead of workflow:execute. An authenticated user with read-only access to a shared workflow can use the Public API to retry…
When was CVE-2026-56778 disclosed?
CVE-2026-56778 was first published in the National Vulnerability Database on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56778 actively exploited?
CVE-2026-56778 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 78.4% of all scored CVEs.
What is the CVSS score of CVE-2026-56778?
CVE-2026-56778 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2026-56778?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56778, 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-56778

Explore →

Is Your Infrastructure Affected by CVE-2026-56778?

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

Start Free Scan →Browse All CVEs