dbcve.org
N8nApplication

CVE-2026-56778

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 2.25.7 / 2.26.2 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

n8n versions before 2.25.7 and 2.26.2 contain an authorization bypass in the Public API execution retry endpoint. The endpoint incorrectly authorizes access using the workflow:read scope instead of the intended workflow:execute scope, allowing authenticated users with read-only access to shared workflows to retry executions.

MitigationUpgrade n8n to version 2.25.7, 2.26.2, or later to resolve the authorization bypass. Review workflow sharing settings to ensure only necessary access is granted until patching is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N8nApplication
Affected:< 2.25.7>= 2.26.0, < 2.26.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed n8n version
    Check the version displayed in the n8n UI (typically in the bottom-left corner) or run `npm list n8n` if installed via npm, or check the Docker container tag. Compare against the affected ranges: < 2.25.7 or >= 2.26.0 and < 2.26.2.
    Affected if The installed version falls within the vulnerable ranges (< 2.25.7 or >= 2.26.0 to < 2.26.2).
  2. Verify Public API is enabled
    In the n8n UI, navigate to Settings > API > Public API, or inspect the environment variables/configuration file for `N8N_PUBLIC_API_ENABLED=true` or `N8N_API_ENABLED=true`. The vulnerability only affects environments where the Public API feature is turned on.
    Affected if The Public API is enabled in the n8n instance.
  3. Confirm workflow sharing is configured
    In the n8n UI, go to Settings > Workflows > Workflow Sharing, or check if any workflows have been shared with users other than the owner. The bypass allows read-only shared users to retry executions on shared workflows.
    Affected if Workflow sharing is enabled and workflows have been shared with other users.
  4. Audit user roles on shared workflows
    Review which users have access to shared workflows and identify those granted read-only (viewer) permissions rather than execute permissions. These users could exploit the flaw to retry executions.
    Affected if There are users with read-only (workflow:read) access to shared workflows through the Public API.

You are affected if your n8n version is vulnerable AND the Public API is enabled AND workflows have been shared with users who only have read access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.25.7 / 2.26.2 or later
Fixed in 2.25.72.26.2
Interim mitigation

Upgrade n8n to version 2.25.7, 2.26.2, or later to resolve the authorization bypass. Review workflow sharing settings to ensure only necessary access is granted until patching is complete.

Recommended fix High confidence

Upgrade to n8n version 2.25.7 (for 2.25.x branch) or 2.26.2 (for 2.26.x branch)

  1. Identify your current n8n installation method (Docker, npm, or binary)
  2. Determine your current n8n version by checking the UI or running the version command
  3. For Docker deployments: pull the new image tag (n8nio/n8n:2.25.7 or n8nio/n8n:2.26.2) and recreate the container
  4. For npm installations: run 'npm install -g [email protected]' or 'npm install -g [email protected]' to upgrade to the appropriate version
  5. For binary installations: download and install the new version from the n8n releases page
  6. After upgrade, verify the new version is running and test that the Public API authorization is correctly enforcing workflow:execute scope for retry operations
  7. Ensure your authentication and authorization configurations are properly applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56778 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56778 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data