CVE-2026-44694 is an authenticated server-side request forgery (SSRF) vulnerability in n8n-MCP, an MCP server that exposes n8n node documentation, properties, and operations to AI assistants. According to the provided content, the issue affects versions 2.18.7 through before 2.50.2 and impacts multiple URL-fetching paths: webhook trigger tools, the n8n API client via the N8N_API_URL setting, and per-request URLs supplied through the x-n8n-url header when running in multi-tenant HTTP mode. An authenticated attacker can cause the server to initiate outbound requests to attacker-controlled or otherwise unintended destinations through these mechanisms. The issue is patched in version 2.50.2.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.