Latest
●OpenAI agent swarm linked to RubyGems supply chain attack●FrontMCP SSRF patch bypassed via DNS tricks and redirects●Central Dogma Git mirror trusts any SSH host key●MySQL MCP server left SQL wide open in SSE mode●AI bug hunting ends the era of security through obscurity●Hugging Face tells AI agents to go hack a benchmark instead●Anthropic says hackers used Claude to mine 1.8M Android apps●Anthropic says Claude was abused to automate attacks and weapons work
Sunday, 13 September 2026
8 agent hacks today▲ 7 vs yesterday (1)
The Agentic TimesPowered byVortal

Incident database

n8n-MCP flaws leak telemetry data and misroute multi-tenant n8n API calls

Two vulnerabilities were disclosed in the n8n-MCP server: before 2.51.3 its telemetry sanitizer could retain fragments of URL-shaped node parameters (such as tenant identifiers or secrets in query strings) and send them to the project's anonymous telemetry backend, and before 2.51.2 multi-tenant HTTP deployments silently fell back to the operator's own N8N_API_URL/N8N_API_KEY when per-request headers were missing, letting a tenant execute n8n management calls against the operator's instance. Both issues are fixed in releases 2.51.3 and 2.51.2.

Disclosed 29 May 2026 · Record updated 13 September 2026

Impact

Customer or tenant identifiers, short secrets in query strings and signed request parameters could be stored in telemetry; in shared multi-tenant HTTP deployments an authenticated tenant could cause n8n management calls to run against the operator's own n8n instance.

Our coverage

No articles linked to this incident yet.

Sources

  1. nvd.nist.govhttps://nvd.nist.gov/vuln/detail/CVE-2026-45582
  2. nvd.nist.govhttps://nvd.nist.gov/vuln/detail/CVE-2026-45707