dbcve.org
N8nApplication

CVE-2026-59207

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 2.27.4 or later.
See remediation →
71/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 is an open source workflow automation platform. Prior to 2.27.4 and 2.28.1, the AI Agents feature did not enforce the Allowed HTTP Request Domains restriction configured on credentials when an MCP tool was pointed at an arbitrary URL, allowing a member-level user with use-only access to a shared credential to send its secret to an external server they control. This issue is fixed in versions 2.27.4 and 2.28.1.

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

The AI Agents feature in n8n failed to enforce the Allowed HTTP Request Domains restriction configured on credentials when an MCP (Model Context Protocol) tool was pointed at an arbitrary URL. This allowed a member-level user with use-only access to a shared credential to exfiltrate the credential's secret to an external server they control by specifying their own URL in an MCP tool, bypassing the intended domain allowlist security control.

MitigationUpgrade n8n to version 2.27.4 or 2.28.1 or later. As a compensating control, restrict which users can create or modify MCP tools and monitor for unauthorized external communications.

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.27.4= 2.28.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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 the installed n8n version
    Run 'n8n --version' or check the Docker container tag, or inspect the package.json in the installation directory
    Affected if The version is lower than 2.27.4 or exactly 2.28.0
  2. Determine if MCP tools are configured
    In the n8n UI, navigate to the AI Agents or Tools section and look for any MCP (Model Context Protocol) tool configurations, or query the database for entries in the workflows table where the type contains 'mcp'
    Affected if MCP tools exist in the environment pointing to user-controlled URLs
  3. Verify if credentials have Allowed HTTP Request Domains configured
    Inspect the credentials stored in n8n by accessing the credentials settings UI or database; check if any credential has a non-empty allowedDomains or HTTPallowlist setting defined
    Affected if Credentials have domain allowlist restrictions configured (this indicates the environment relies on this security control)
  4. Check user permissions for MCP tool creation
    Review the n8n role-based access control settings; determine which users have permission to create or modify AI Agent tools, specifically MCP tools
    Affected if Member-level users or users with only use-only access to shared credentials can create or modify MCP tools

You are affected if your n8n version is below 2.27.4 or exactly 2.28.0, MCP tools are in use, and users with limited permissions can configure MCP tools to point to arbitrary URLs, bypassing the credential domain allowlist.

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.27.4 or later
Fixed in 2.27.4
Interim mitigation

Upgrade n8n to version 2.27.4 or 2.28.1 or later. As a compensating control, restrict which users can create or modify MCP tools and monitor for unauthorized external communications.

Recommended fix High confidence

n8n version 2.27.4 or 2.28.1 (depending on your current version)

  1. Identify the current n8n version in use by checking the container, package.json, or n8n instance
  2. Backup all n8n data including workflows, credentials, and settings
  3. For n8n versions below 2.27.4: Upgrade to version 2.27.4
  4. For n8n version 2.28.0: Upgrade to version 2.28.1
  5. Verify the upgrade was successful by checking the n8n version after restart
  6. Confirm the Allowed HTTP Request Domains restriction is now enforced for MCP tools in AI Agents

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

Fix this in N8n Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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