Miggo at BlackHat 2026!
Easily map the attack path and prioritize which CVEs are a threat to your organization
Miggo AIGenerate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| n8n-mcp | npm | < 2.51.3 | 2.51.3 |
Miggo AIRoot Cause AnalysisThe vulnerability exists in the telemetry sanitization process of n8n-mcp. When preparing workflow data for anonymous telemetry, the sanitizer attempted to anonymize fields that appeared to be URLs (e.g., field names containing 'url', 'endpoint', or 'webhook'). The flaw was in the implementation of this anonymization. Instead of redacting the entire URL, the WorkflowSanitizer.sanitizeString function would only replace the domain/hostname part of the URL, while leaving the path and query string parameters intact. This was problematic because sensitive information, such as customer identifiers, tenant names, or short-lived tokens, is often passed in the URL path or query string. The WorkflowSanitizer.sanitizeObject function was responsible for identifying these URL-like fields and passing them to the faulty sanitizeString function. The patch corrects this by removing the partial sanitization logic entirely and instead fully redacting any field identified as a sensitive URL with [REDACTED_URL]. This ensures that no part of the URL that could contain sensitive data is leaked into the telemetry backend.
WorkflowSanitizer.sanitizeObjectsrc/telemetry/workflow-sanitizer.ts
WorkflowSanitizer.sanitizeStringsrc/telemetry/workflow-sanitizer.ts