# CVE-2026-44694: n8n-MCP: Authenticated SSRF in n8n-mcp webhook and API client paths

> Authenticated attackers can exploit SSRF in n8n-MCP webhook and API client paths to access internal resources or bypass security controls.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/SC:H/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-cmrh-wvq6-wm9r

## What is CVE-2026-44694?

CVE-2026-44694 is a high-severity server-side request forgery vulnerability in czlonkowski n8n-mcp, published on 8 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. From version 2.18.7 to before version 2.50.2, there is an authenticated server-side request forgery vulnerability affecting the webhook trigger tools, the n8n API client (N8N_API_URL), and per-request URLs supplied via the x-n8n-url header in multi-tenant HTTP mode. This issue has been patched in version 2.50.2.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2026-44694?

2 open source packages ship an affected version, including n8n-mcp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `n8n-mcp` | npm | From 2.18.7 | 2.50.2 |
| `n8n-mcp` | npm | From 2.18.7 | 2.50.2 |

Products: N8n-Mcp N8n-Mcp.

## How do I fix CVE-2026-44694?

Upgrade n8n-mcp to 2.50.2 or later.

## Is CVE-2026-44694 being exploited?

There is no known exploitation of CVE-2026-44694 in the wild and no public exploit code.

## Other vulnerabilities in czlonkowski n8n-mcp

- [CVE-2026-54052](https://insights.sbomify.com/CVE-2026-54052/): n8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deployments (critical 9.9)
- [CVE-2026-42449](https://insights.sbomify.com/CVE-2026-42449/): n8n-MCP: IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embedders (high 8.5)
- [CVE-2026-39974](https://insights.sbomify.com/CVE-2026-39974/): n8n-MCP has an Authenticated SSRF via instance-URL header in multi-tenant HTTP mode (high 8.5)
- [CVE-2026-45707](https://insights.sbomify.com/CVE-2026-45707/): n8n-MCP: Multi-tenant MCP requests fall back to process-level n8n credentials when tenant headers are absent or incomplete (high 8.1)
- [CVE-2026-45582](https://insights.sbomify.com/CVE-2026-45582/): n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44694 and fix it if it is affected.

What it is: CVE-2026-44694 is a high-severity server-side request forgery vulnerability in czlonkowski n8n-mcp, published on 8 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44694 in the wild and no public exploit code.

Affected packages and fixed versions:
- n8n-mcp (npm): affected from 2.18.7; fixed in 2.50.2
- n8n-mcp (npm): affected from 2.18.7; fixed in 2.50.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44694/ (Markdown: https://insights.sbomify.com/CVE-2026-44694/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44694
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44694
- OSV: https://osv.dev/vulnerability/CVE-2026-44694

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44694/
Summaries are generated and may contain mistakes; the official description above is the record.