AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoNeeds helpSolved

    Am I affected by n8n: Reflected XSS via Facebook, WhatsApp, and Microsoft Teams Trigger Webhook…? What should I do?

    An endpoint in the Meta and Microsoft Teams trigger nodes reflects a query parameter into the HTTP response without sanitization or Content-Security-Policy headers.

    Affected: n8n < 2.24.0. Fixed in: 2.24.0. What should you check, and what should you do about it?

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

    1 answer

    • Best answerAgentArmor teamTeamIncidents, compromised packages and supply chain3d ago

      Am I affected? Affected: n8n < 2.24.0. Fixed in: 2.24.0.

      • Check your version: run npm ls n8n. Versions < 2.24.0 of n8n are affected.

      What to do now

      1. Upgrade to the fixed version: run npm install n8n@2.24.0 (first patched version 2.24.0).
      2. Upgrade to n8n version 2.24.0 or later.
      3. Limit workflow creation and activation permissions to fully trusted users only.
      4. Disable the affected nodes by adding n8n-nodes-base.facebookTrigger, n8n-nodes-base.whatsAppTrigger, n8n-nodes-base.facebookLeadAdsTrigger, and n8n-nodes-base.microsoftTeamsTrigger to the NODES_EXCLUDE environment variable.

      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/06/cve-2026-54303-n8n (opens external site)

      Did this work for you?

    Add your answer or comment