{"answers":{"affected":"2 open source packages ship an affected version, including n8n-mcp. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44694 in the wild and no public exploit code.","fix":"Upgrade n8n-mcp to 2.50.2 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-44694 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-44694 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- n8n-mcp (npm): affected from 2.18.7; fixed in 2.50.2\n- n8n-mcp (npm): affected from 2.18.7; fixed in 2.50.2\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44694/ (Markdown: https://insights.sbomify.com/CVE-2026-44694/index.md)","id":"CVE-2026-44694","markdown":"https://insights.sbomify.com/CVE-2026-44694/index.md","name":"CVE-2026-44694","record":{"aliases":["GHSA-cmrh-wvq6-wm9r"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"n8n MCP server","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit SSRF in n8n-MCP webhook and API client paths to access internal resources or bypass security controls.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"n8n-mcp","vendor":"n8n-mcp"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"n8n-MCP: Authenticated SSRF in n8n-mcp webhook and API client paths","id":"CVE-2026-44694","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Outline: Slack OAuth state can link a victim Outline account to an attacker Slack identity","id":"CVE-2026-44695"},"packages":[{"ecosystem":"npm","fixed":["2.50.2"],"introduced":["2.18.7"],"last_affected":[],"package":"n8n-mcp","purl":null,"source":"GHSA-cmrh-wvq6-wm9r"},{"ecosystem":"npm","fixed":["2.50.2"],"introduced":["2.18.7"],"last_affected":[],"package":"n8n-mcp","purl":"pkg:npm/n8n-mcp","source":"GHSA-cmrh-wvq6-wm9r"}],"prev":{"headline":"Pi-hole FTL: Unauthenticated Session Hijacking via Race Condition on Global Session Buffer","id":"CVE-2026-44693"},"products":["n8n-mcp"],"published":"2026-05-08","related":[{"cvss_score":9.9,"headline":"n8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deployments","id":"CVE-2026-54052","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":8.5,"headline":"n8n-MCP: IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embedders","id":"CVE-2026-42449","kev_date_added":null,"published":"2026-05-07"},{"cvss_score":8.5,"headline":"n8n-MCP has an Authenticated SSRF via instance-URL header in multi-tenant HTTP mode","id":"CVE-2026-39974","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":8.1,"headline":"n8n-MCP: Multi-tenant MCP requests fall back to process-level n8n credentials when tenant headers are absent or incomplete","id":"CVE-2026-45707","kev_date_added":null,"published":"2026-05-29"},{"cvss_score":6.5,"headline":"n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters","id":"CVE-2026-45582","kev_date_added":null,"published":"2026-05-29"},{"cvss_score":5.3,"headline":"n8n-MCP Logs Sensitive Request Data on Unauthorized /mcp Requests","id":"CVE-2026-41495","kev_date_added":null,"published":"2026-05-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-12","vendors":["czlonkowski"]},"summary":"Authenticated attackers can exploit SSRF in n8n-MCP webhook and API client paths to access internal resources or bypass security controls.","url":"https://insights.sbomify.com/CVE-2026-44694/"}