dbcve.org
N8nApplication

CVE-2026-56359

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 2.6.4 / 2.8.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 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.8.0 contains a cross-site scripting vulnerability in the credential management flow where authenticated users can inject malicious JavaScript URLs into OAuth2 credential Authorization URL fields. Attackers can craft malicious credentials and trick victims into clicking the OAuth authorization button, executing arbitrary scripts in their browser session with the victim's privileges.

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

This is a stored cross-site scripting (XSS) vulnerability in n8n's OAuth2 credential management. Authenticated attackers can inject malicious JavaScript URLs into the Authorization URL field of OAuth2 credentials. When victims click the OAuth authorization button on these crafted credentials, the embedded script executes in their browser session with the victim's privileges.

MitigationUpgrade to n8n version 2.8.0 or later which contains the fix for this vulnerability. Until then, limit credential management permissions to trusted users and monitor for suspicious OAuth credential configurations.

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.6.4>= 2.7.0, < 2.8.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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
    Run 'n8n --version' or check the Docker container/tag version, or query the API endpoint '/rest/version'
    Affected if Version is < 2.6.4 or >= 2.7.0 and < 2.8.0
  2. List OAuth2 credentials
    Access n8n UI: Credentials section, filter by type 'OAuth2' or 'oAuth2 API'; or query via API: GET /rest/credentials?type=oAuth2Api
    Affected if Any OAuth2 credentials exist in the system
  3. Inspect Authorization URL fields
    Open each OAuth2 credential and examine the 'Authorization URL' field for suspicious patterns: 'javascript:' protocol, '<script>', 'onerror=', 'onclick=', 'eval(', 'alert(', URL-encoded XSS vectors
    Affected if Any OAuth2 credential contains JavaScript code or XSS payloads in the Authorization URL field
  4. Review credential modification logs
    Check n8n audit logs or external logging for recent creates/updates to OAuth2 credentials, especially by users who should not have credential access
    Affected if OAuth2 credentials were recently created or modified by untrusted users

You are affected if your n8n version is < 2.6.4 or >= 2.7.0 and < 2.8.0 AND any OAuth2 credentials contain JavaScript or XSS payloads in their Authorization URL fields.

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.6.4 / 2.8.0 or later
Fixed in 2.6.42.8.0
Interim mitigation

Upgrade to n8n version 2.8.0 or later which contains the fix for this vulnerability. Until then, limit credential management permissions to trusted users and monitor for suspicious OAuth credential configurations.

Recommended fix High confidence

n8n version 2.8.0 or later

  1. 1. Back up your n8n instance database and configuration files before upgrading.
  2. 2. Review the n8n 2.8.0 release notes for any breaking changes or migration requirements.
  3. 3. For Docker installations: Stop the container, pull the new image tag (n8nio/n8n:2.8.0 or later), and restart the container.
  4. 4. For npm installations: Run 'npm install -g [email protected]' or 'npm install -g n8n@latest' to get the fixed version.
  5. 5. After upgrading, verify that existing OAuth2 credentials work correctly and that the Authorization URL fields are properly sanitized.
  6. 6. Clear any browser cache to ensure the updated frontend is loaded.
Caveat Review n8n 2.8.0 release notes for any breaking changes; minor version upgrades typically have minimal impact but always test first

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

Fix this in N8n Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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