dbcve.org
N8nApplication

CVE-2026-56775

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 1.123.55 / 2.25.7 or later.
See remediation →
60/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 1.123.55, 2.25.7, and 2.26.2 contains an authorization vulnerability in three mutating evaluation test-run endpoints that authorize state-changing actions using the workflow:read scope instead of the action-appropriate workflow:execute scope. On instances using Advanced Permissions (Enterprise/Cloud) with projects and viewer roles, an authenticated user with the project:viewer role can start new evaluation test runs, cancel in-flight runs, and delete run records for workflows they only have read access to.

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 prior to 1.123.55, 2.25.7, and 2.26.2 have an authorization bypass in three evaluation test-run endpoints (start, cancel, delete). These mutating endpoints incorrectly check for workflow:read scope instead of workflow:execute scope, allowing project:viewer role users to perform execute-level actions on workflows they can only read.

MitigationUpgrade n8n to version 1.123.55, 2.25.7, 2.26.2 or later. Until upgraded, disable viewer role access to workflows or audit permissions in Advanced Permissions environments.

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:< 1.123.55>= 2.0.0, < 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
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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
    Run `n8n --version` from the command line, or check the version displayed in the n8n UI footer, or inspect the package.json file in the n8n installation directory
    Affected if The version is less than 1.123.55, or between 2.0.0 and 2.25.6, or between 2.26.0 and 2.26.1
  2. Confirm Advanced Permissions are enabled
    In the n8n UI, navigate to Settings > Advanced Permissions, or check the N8N_PERMISSIONS_MODE environment variable is set to 'advanced'
    Affected if Advanced Permissions mode is enabled and viewer roles exist in the system
  3. Verify viewer role users exist with workflow access
    In n8n, go to Settings > Users and review role assignments, or query the database for users with 'viewer' project role who have been granted workflow access
    Affected if Any user holds the project:viewer role and has access to at least one workflow
  4. Check for recent test-run API activity from viewer accounts
    Review n8n audit logs or API access logs for POST/DELETE requests to /workflows/{id}/run, /workflows/{id}/cancel, or /workflows/{id}/delete endpoints made by users with viewer permissions
    Affected if Viewer role users have successfully executed start, cancel, or delete operations on workflows through the API

You are affected if your n8n version falls within the vulnerable ranges AND you have project:viewer role users with workflow access using Advanced Permissions mode.

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 1.123.55 / 2.25.7 / 2.26.2 or later
Fixed in 1.123.552.25.72.26.2
Interim mitigation

Upgrade n8n to version 1.123.55, 2.25.7, 2.26.2 or later. Until upgraded, disable viewer role access to workflows or audit permissions in Advanced Permissions environments.

Recommended fix High confidence

1.123.55 (for 1.x) or 2.25.7 (for 2.0.0-2.25.x) or 2.26.2 (for 2.26.x)

  1. 1. Identify your current n8n version by checking the n8n instance or running `n8n --version`
  2. 2. If running version 1.x: Upgrade to version 1.123.55 or later
  3. 3. If running version 2.0.0 to 2.25.6: Upgrade to version 2.25.7 or later
  4. 4. If running version 2.26.0 to 2.26.1: Upgrade to version 2.26.2 or later
  5. 5. Verify the upgrade was successful by checking the n8n version
  6. 6. Confirm that users with project:viewer role can no longer start, cancel, or delete evaluation test runs for workflows they only have read access to

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

Fix this in N8n Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56775 — 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-56775 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