p PatchFirst

CVE-2026-39974

CVE-2026-39974 · n8n-MCP has an Authenticated SSRF via instance-URL header in multi-tenant HTTP mode

Cette page présente des faits issus de sources publiques. Consultez l’avis original avant toute mise à jour.

n8n-MCP is a Model Context Protocol (MCP) server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations. Prior to 2.47.4, an authenticated Server-Side Request Forgery in n8n-mcp allows a caller holding a valid AUTH_TOKEN to cause the server to issue HTTP requests to arbitrary URLs supplied through multi-tenant HTTP headers. Response bodies are reflected back through JSON-RPC, so an attacker can read the contents of any URL the server can reach — including cloud instance metadata endpoints (AWS IMDS, GCP, Azure, Alibaba, Oracle), internal network services, and any other host the server process has network access to. The primary at-risk deployments are multi-tenant HTTP installations where more than one operator can present a valid AUTH_TOKEN, or where a token is shared with less-trusted clients. Single-tenant stdio deployments and HTTP deployments without multi-tenant headers are not affected. This vulnerability is fixed in 2.47.4.

CVSS 8.5 · Élevée · EPSS 0,3% · Correctif disponible

Publication
Mise à jour

Pile logicielle: node

Produits et versions concernés

  • n8n-mcp

    Versions du logiciel
    • < 2.47.4: Concernée

    Aucun correctif publié

  • n8n-mcp npm

    Plages de versions concernées
    • SEMVER: < 2.47.4

    Mettez à jour vers 2.47.4

Sources originales

Vérifiez votre serveur →