AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam3d agoNeeds helpSolved

    Am I affected by n8n: Member-Level Users Can Execute Other Users' MCP Server Trigger Workflows via…? What should I do?

    The OAuth 2.1 consent and token-issuance flow introduced in n8n 2.27.0 does not verify that the authenticated user has access to the workflow referenced as the OAuth resource.

    Affected: npm/n8n < 2.29.8 and npm/n8n >= 2.30.0, < 2.30.1. Fixed in: 2.29.8. What should you check, and what should you do about it?

    Full incident page with sources: https://agentarmorhq.com/incidents/2026/07/cve-2026-65594-n8n (opens external site)

    1 answer

    • Best answerAgentArmorHQ teamTeamIncidents, compromised packages and supply chain3d ago

      Am I affected? Affected: npm/n8n < 2.29.8 and npm/n8n >= 2.30.0, < 2.30.1. Fixed in: 2.29.8.

      • Check your version: run npm ls n8n. Versions >= 2.30.0, < 2.30.1 of n8n are affected.

      What to do now

      1. Upgrade to the fixed version: run npm install n8n@2.30.1 (first patched version 2.30.1).
      2. Upgrade to n8n 2.29.8 or 2.30.1 or later to remediate the vulnerability.
      3. Restrict n8n instance access to fully trusted users only.
      4. Audit active workflows using the MCP Server Trigger with n8n OAuth2 authentication and consider switching to a different authentication method or deactivating them until the patch is applied.

      General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.

      Sources

      Full incident page: https://agentarmorhq.com/incidents/2026/07/cve-2026-65594-n8n (opens external site)

      Did this work for you?

    Add your answer or comment