AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam4d agoNeeds helpSolved

    Am I affected by n8n: Microsoft SQL Node Prototype Pollution? What should I do?

    An authenticated user with permission to create or modify workflows could achieve global prototype pollution via the Microsoft SQL node by supplying a crafted value as the table parameter.

    Affected: npm/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-54312-n8n (opens external site)

    1 answer

    • Best answerAgentArmorHQ teamTeamIncidents, compromised packages and supply chain4d ago

      Am I affected? Affected: npm/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 editing permissions to fully trusted users only.
      4. Disable the Microsoft SQL node by adding n8n-nodes-base.microsoftSql 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-54312-n8n (opens external site)

      Did this work for you?

    Add your answer or comment