AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoNeeds helpSolved

    Am I affected by n8n: "Allowed HTTP Request Domains" Restriction Bypass via AI Agents MCP Connector? What should I do?

    The AI Agents feature did not enforce the "Allowed HTTP Request Domains" restriction configured on credentials.

    Affected: n8n >= 2.28.0, < 2.28.1 and n8n < 2.27.4. Fixed in: 2.28.1 and 2.27.4. What should you check, and what should you do about it?

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

    1 answer

    • Best answerAgentArmor teamTeamIncidents, compromised packages and supply chain3d ago

      Am I affected? Affected: n8n >= 2.28.0, < 2.28.1 and n8n < 2.27.4. Fixed in: 2.28.1 and 2.27.4.

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

      What to do now

      1. Upgrade to the fixed version: run npm install n8n@2.28.1 (first patched version 2.28.1).
      2. Upgrade to n8n version 2.28.1 or 2.27.4 or later.
      3. Disable the AI Agents module by removing agents from the N8N_ENABLED_MODULES environment variable.
      4. Restrict credential sharing to fully trusted users only.
      5. Audit credentials with domain restrictions for unexpected sharing relationships.

      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-59207-n8n (opens external site)

      Did this work for you?

    Add your answer or comment