CVE-2026-72768
highPriorität · verfolgen · 33EPSS 0.004 · 34. PerzentilDEEUUSEPSS · bewertet 2026-10-27
n8n versions before 2.32.1 contain a server-side request forgery protection bypass vulnerability in the MCP Client node that allows authenticated users to bypass SSRF protections. Attackers can craft workflows that send requests to internal or blocked hosts without routing through SSRF protection, exposing internal services and reading responses back through the workflow.
cvss
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · low–high · 2.5–8.3
SSVC
Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
betroffene Produkte (12)
Betroffene Produkte und Versionsbereiche.
Advisories (2)
Hersteller- und Ökosystem-Meldungen dazu.
- WID-SEC-W-2026-2489n8n: Mehrere SchwachstellenDeutsch2026-07-22csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen SQL-Injection Angriff durchzuführen, und um beliebigen Programmcode auszuführen.
- GHSA-vhf8-cg2h-cg3pn8n: SSRF Protection Bypass via MCP Client Node2026-07-22ghsa · osvUS
## Impact On an n8n instance with SSRF protection enabled, the MCP Client node sent requests to a user-supplied endpoint without routing them through that protection and without pinning the resolved address. An authenticated user who could create or edit a workflow could therefore cause the server to connect to internal or otherwise blocked hosts and read the responses back through the workflow, exposing internal services the SSRF protection was meant to protect. ## Patches The issue has been fixed in n8n versions 2.31.5 and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n instance access to fully trusted users only. - Disable the MCP Client node by adding it to the `NODES_EXCLUDE` environment variable. - Restrict network egress from the n8n host to block access to internal and link-local address ranges at the network level. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
auch bekannt als (3)
Weitere Namen und Kennungen dieser Entität.
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (6)
Externe Belege — Patches, Meldungen, Analysen.
- https://github.com/n8n-io/n8n/security/advisories/GHSA-vhf8-cg2h-cg3pcnnvd
- https://www.vulncheck.com/advisories/n8n-before-ssrf-protection-bypass-via-mcp-clientcnnvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-vhf8-cg2h-cg3penisa_euvd
- https://www.vulncheck.com/advisories/n8n-before-ssrf-protection-bypass-via-mcp-clientenisa_euvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-vhf8-cg2h-cg3pMitigationVendor Advisorynvd
- https://www.vulncheck.com/advisories/n8n-before-ssrf-protection-bypass-via-mcp-clientThird Party Advisorynvd
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan