Skip to content

AAK-MCP-N8N-CVE-2026-59207-001: n8n below 2.41.4 / 2.42.0 (webhook, form and MCP routes run any project's workflow without its identifier; MCP tool bypasses the credential domain allow-list)

Severity
MEDIUM
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
N8nMcpCredentialDomainBypass

What it detects

n8n before 2.27.4 (and the 2.28.x line before 2.28.1) did not enforce the "Allowed HTTP Request Domains" restriction on credentials when an AI-Agent MCP tool was pointed at an arbitrary URL, letting a member-level user with use-only access to a shared credential send its secret to an external server they control (CVE-2026-59207, CVSS 6.5). On the 1.x line before 1.123.83, on 2.x before 2.41.4 and at 2.42.0, dynamic-path webhook resolution matches a request on its path alone and ignores the server-generated identifier that is the URL's only unguessable part, so an unauthenticated caller who leaves it out reaches webhook, form and MCP routes and runs workflows in unrelated projects under those projects' credentials (CVE-2026-110852, CVSS 4.0 6.3). That fix is above the old 2.27.4 floor and the CVE is MEDIUM, as the rule is, so the floor rose to 2.41.4, with a range for 2.42.0, which sorts above it and is still affected. A project pinning n8n below 2.41.4, or on 2.42.0, or leaving it unpinned, is exposed to at least one of these.

How to fix

Upgrade n8n to >= 2.41.4 and pin it, or to >= 2.42.1 on the 2.42.x line; a 1.x deployment needs 1.123.83 for the webhook bypass and 2.x for the credential-domain one. Enforce the credential domain allow-list on MCP/HTTP tool destinations so a member-level user cannot redirect a shared credential to an external host.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-N8N-CVE-2026-59207-001

Limitations

Reads n8n in requirements*.txt at any depth and, at the project root only, in pyproject.toml, Pipfile, package.json, .mcp.json, mcp.json, claude_desktop_config.json and the Pipfile.lock, poetry.lock, uv.lock, package-lock.json, pnpm-lock.yaml and yarn.lock lockfiles, taking the lowest version a range allows and reporting a reference that states no version. Every 1.x release is reported, because all of them are below the 2.27.4 fix for CVE-2026-59207, although 1.123.83 and later fix the webhook bypass. The dependency is not read when it is declared in a sub-directory manifest (packages/app/package.json) or in a lockfile format the reader does not parse (a Yarn 2+ yarn.lock). A compose file's n8nio/n8n image tag is not read. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References

  • CVE: CVE-2026-59207, CVE-2026-110852
  • OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP05:2025 (Command Injection & Execution), MCP07:2025 (Insufficient Authentication & Authorization)
  • OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation), ASI03 (Identity and Privilege Abuse), ASI04 (Agentic Supply Chain Vulnerabilities)
  • Adversa AI MCP Top 25 (AAK-defined ids): ADV-SSRF-01 (Internal Network MCP), ADV-AUTH-01 (Missing Authentication)
  • CSA AI Controls Matrix (AICM): IVS-04, STA-08

All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-N8N-CVE-2026-59207-001.md: the page then shows that text, with the registry reference appended under it.