CVE-2026-56778

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreHIGH 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 — 4 sources updated this week
6.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.4Exploit: NoneExposed: 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(high)
EPSS
7.1%
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.26.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 24× 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-15 02:00 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-15 00:44 UTCEG score recompute
  4. 2026-07-15 00:44 UTCGHSA enrichment
  5. 2026-07-13 22:58 UTCEG score recompute
  6. 2026-07-13 22:58 UTCGHSA enrichment
  7. 2026-07-13 22:31 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-12 21:12 UTCEG score recompute
  11. 2026-07-12 21:12 UTCGHSA enrichment
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-11 19:25 UTCEG score recompute
  14. 2026-07-11 19:25 UTCGHSA enrichment
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-10 17:40 UTCEG score recompute
  18. 2026-07-10 17:39 UTCGHSA enrichment
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-09 15:53 UTCEG score recompute
  22. 2026-07-09 15:53 UTCGHSA enrichment
  23. 2026-07-08 14:06 UTCEG score recompute
  24. 2026-07-08 14:05 UTCMITRE cvelistV5first tracked

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 7.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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