SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2026-42449Public Intelligence Dossier
Source: n8n-mcp · Limited verification•Last verified: •Collection Degraded
CVE-2026-42449Unknown / EvaluatingHIGH (raw)CVSS 8.5CWE-918

n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations

Published: 08 May 2026•Last updated: 27 Oct 2026, 01:40 AM IST•Source identifier: security-advisories@github.com
Dossier completeness: source-provided sections 2 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Unknown
KEV status was not determined.
CVSS score
8.5HIGH (raw)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Metric sourcesecurity-advisories@github.com
EPSS probability
0.2%0.002
Percentile11th
Weakness type
CWE-918
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. In versions 2.47.4 through 2.47.13, the SDK embedder path (N8NDocumentationMCPServer constructor, getN8nApiClient(), and validateInstanceContext()), the synchronous URL validator in SSRFProtection.validateUrlSync() had no IPv6 checks. IPv4-mapped IPv6 addresses such as http://[::ffff:169.254.169.254] bypassed the cloud-metadata, localhost, and private-IP range checks. An attacker able to supply an n8nApiUrl value could cause the server to issue HTTP requests to cloud metadata endpoints, RFC1918 private networks, or localhost services. Response bodies are returned to the caller (non-blind SSRF), and the n8nApiKey is forwarded in the x-n8n-api-key header to the attacker-controlled target. Projects with deployments embedding n8n-mcp as an SDK using N8NDocumentationMCPServer or N8NMCPEngine with user-supplied InstanceContext are affected. The first-party HTTP server deployment was not primarily affected — it has a second async validator (validateWebhookUrl) that catches IPv6 addresses. This issue has been fixed in version 2.47.14. If users are unable to upgrade immediately as a workaround they can validate URLs before passing to the SDK, restrict egress at the network layer, and reject user-controlled n8nApiUrl values.

SOC priority

High

Actively exploited (source statement)

Unknown

Publicly disclosed

Unknown

Risk basis: SOC ecosystem technology relevance; HIGH severity; Source severity; no confirmed exploitation signal

Affected Products & Remediation

1 source-backed product
Affected products and versions (source)
  • n8n-mcp n8n-mcp · >= 2.47.4 < 2.47.14 · NVD CPE · Source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

Not provided by source

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Unknown
Exploited (source statement)
Unknown
Publicly disclosed (source)
Unknown

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched ssrf (CWE-918)

Exposure

  1. Identify affected server-side request features and deployed versions.Telemetry: Application inventory · The specific feature must be confirmed from the advisory. · Rule ssrf

Exploitation evidence

  1. Review unusual outbound connections from the affected service to internal or metadata endpoints.Telemetry: DeviceNetworkEvents · Outbound patterns can support SSRF hunting. · Rule ssrf

Response

  1. Verify the vendor fix and confirm expected egress after deployment.Telemetry: DeviceNetworkEvents · Post-change telemetry helps validate mitigation. · Rule ssrf

CISA KEV Record

CISA KEV status was not determined for this record.

Change History & Source Data

— No recorded material change

CNA / source
security-advisories@github.com
Record status · verification
UPDATED · NVD API
CPE
cpe:2.3:a:n8n-mcp:n8n-mcp:*:*:*:*:*:*:*:*

Evidence & Provenance

3 public sources
github.comSource recordnvd.nist.govSource recordgithub.comSource record

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2026-42449
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2026-42449
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2026-42449"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Open KQL Library

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.