dbcve.org
N8nApplication

CVE-2026-54307

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 1.123.55 / 2.25.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, a member-level user with editor access to a shared workflow could reference credentials they do not own via specific public API endpoints. Credential ownership checks were only enforced partially leading to cross-user credential access. This issue affects instances where workflow sharing is enabled and at least one workflow has been shared with a member-level user as an Editor. This vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.2.

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

In n8n workflow automation platform prior to versions 1.123.55, 2.25.7, and 2.26.2, a member-level user with editor access to a shared workflow could reference credentials they do not own via specific public API endpoints due to incomplete credential ownership checks, enabling cross-user credential access.

MitigationUpgrade n8n to version 1.123.55, 2.25.7, or 2.26.2. Additionally, audit shared workflows and credentials to identify any unauthorized access that may have occurred.

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
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 n8n version by running 'n8n --version' from command line, or inspecting the package.json file in the n8n installation directory, or querying the n8n API health endpoint if accessible.
    Affected if The installed version is below 1.123.55 for 1.x releases, or below 2.25.7 for 2.0.0-2.25.x releases, or below 2.26.2 for 2.26.x releases.
  2. Confirm member-level users exist
    Review user management settings or user database to identify accounts with member-level roles, particularly those who have been granted editor access to workflows owned by other users.
    Affected if There are member-level users who have been given editor or contributor access to workflows owned by different users.
  3. Audit shared workflow configurations
    Examine which workflows have been shared with member-level users, particularly workflows that reference credentials. Check the workflow sharing settings to see which non-owner users have access.
    Affected if Shared workflows exist where member-level users have editor access and the workflows reference credentials owned by different users.
  4. Review API access logs for credential-related endpoints
    Inspect API access logs or audit trails for requests to credential-related endpoints (such as /credentials/ or /workflows/ with credential parameters) made by member-level users accessing credentials they do not own.
    Affected if API logs show member-level users successfully retrieving or referencing credential details for credentials owned by other users.

A user is affected if running a vulnerable n8n version AND member-level users have been granted editor access to shared workflows that reference credentials owned by other users.

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, or 2.26.2. Additionally, audit shared workflows and credentials to identify any unauthorized access that may have occurred.

Recommended fix High confidence

Upgrade to 1.123.55 (for 1.x users), 2.25.7 (for 2.0-2.25.x users), or 2.26.2 (for 2.26.x users)

  1. Identify your current n8n version by checking the instance or package.json
  2. If running version 1.x: upgrade to version 1.123.55 or later (e.g., 1.123.55, 1.124.0)
  3. If running version 2.0.0 through 2.25.x: upgrade to version 2.25.7 or later (e.g., 2.25.7, 2.26.0)
  4. If running version 2.26.0 through 2.26.x: upgrade to version 2.26.2 or later (e.g., 2.26.2)
  5. After upgrade, verify the instance starts successfully and test that credential access controls are working correctly

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

Fix this in N8n Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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