CVE-2026-54305
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 · uneditedn8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, three EE endpoints used by the Dynamic Credentials feature accepted any authenticated n8n session without performing per-resource ownership or scope checks on the target workflow or credential. An authenticated user with no project membership or credential sharing relationship could enumerate credential identifiers, names, and types referenced by any private workflow in the instance, initiate an OAuth authorization flow against another user's credential to overwrite its stored tokens with tokens bound to an account they control, or revoke another user's stored credential tokens entirely. Workflows relying on a hijacked credential would subsequently execute under the attacker's OAuth identity, enabling data exfiltration to attacker-controlled external services and persistent takeover of integrations. Token revocation would break affected workflows. 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 confidencen8n's Dynamic Credentials feature had three EE endpoints that failed to perform per-resource ownership or scope validation, allowing any authenticated session user to access, enumerate, or manipulate credentials associated with any private workflow. Attackers could hijack OAuth authorization flows to overwrite token stores with their own identity, or revoke tokens entirely, causing affected workflows to execute under the attacker's OAuth identity for data exfiltration or persistent integration takeover.
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< 1.123.55>= 2.0.0, < 2.25.7>= 2.26.0, < 2.26.2CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine n8n versionRun `n8n --version` from the command line, check the Docker image tag, or inspect the package.json file in the n8n installation directoryAffected if The installed 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
-
Confirm Enterprise Edition usageCheck if the installation is running EE edition by inspecting the license file, environment variable N8N_EDITION, or checking the /license endpoint responseAffected if The instance is running Enterprise Edition (EE) as the vulnerable endpoints are EE-specific
-
Identify Dynamic Credentials usageQuery the database or API for workflows utilizing the Dynamic Credentials feature - check workflow JSON for nodes with credential type references or inspect the credentials table for entries with dynamic scopesAffected if Any workflows are using Dynamic Credentials with OAuth-based credential types
-
Audit OAuth credential configurationsReview stored OAuth credentials via the API endpoint /credentials or database inspection of the credentials table, noting which credentials are linked to which workflows and usersAffected if OAuth-based credentials exist that are shared across workflows or users beyond the credential owner
You are affected if running a vulnerable n8n version (less than 1.123.55, 2.25.7, or 2.26.2) with Enterprise Edition and have workflows using Dynamic Credentials with OAuth-based integrations.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.123.552.25.72.26.2
Upgrade n8n to version 1.123.55, 2.25.7, or 2.26.2 or later. Additionally, audit credential usage logs and OAuth authorization history for unauthorized access patterns, and rotate any credentials that may have been compromised.
Upgrade to n8n 1.123.55 (if on 1.x) or 2.25.7/2.26.2 (if on 2.x)
- 1. Identify the currently running n8n version using `n8n --version` or checking the container/image tag
- 2. For n8n < 1.123.55: Upgrade to version 1.123.55 or later
- 3. For n8n >= 2.0.0, < 2.25.7: Upgrade to version 2.25.7 or later
- 4. For n8n >= 2.26.0, < 2.26.2: Upgrade to version 2.26.2 or later
- 5. After upgrading, verify the installation by checking the n8n version with `n8n --version`
- 6. Review any workflows using Dynamic Credentials to ensure they still function correctly after the security fix
- 7. Consider rotating any credentials that may have been compromised during the vulnerability window
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54305 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54305 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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