High (AgentArmorHQ estimate)Data leak

n8n: SecurityScorecard Node Leaks API Token to User-Controlled Host

Product
n8n
CVE
CVE-2026-54304
Affected
npm/n8n < 1.123.55; npm/n8n >= 2.0.0-rc.0, < 2.25.7; npm/n8n >= 2.26.0, < 2.26.1
Fixed in
1.123.55, 2.25.7, 2.26.1

Last verified against sources: October 26, 2026

Am I affected?

n8n: affected npm/n8n < 1.123.55; npm/n8n >= 2.0.0-rc.0, < 2.25.7; npm/n8n >= 2.26.0, < 2.26.1. Fixed in 1.123.55, 2.25.7, 2.26.1.

  • Check your version: run npm ls n8n. Versions < 1.123.55 of n8n are affected. [1]

What to do now

  1. Upgrade to the fixed version: run npm install n8n@1.123.55 (first patched version 1.123.55). [1]
  2. Upgrade to n8n 1.123.55, 2.25.7, or 2.26.1 or later to remediate the vulnerability. [1]
  3. Limit workflow creation and editing permissions to fully trusted users only. [1]
  4. Disable the SecurityScorecard node by adding n8n-nodes-base.securityScorecard to the NODES_EXCLUDE environment variable. [1]

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.

Discuss this incident

What happened

  • An authenticated user with permission to create or modify workflows and access to a SecurityScorecard credential with limited allowed domains could configure the SecurityScorecard node's report download operation to target an attacker-controlled URL. [1]
  • The node attached the SecurityScorecard API token to the outbound request. [1]

Impact

  • The credential was sent to the attacker-controlled host bypassing credential configured limitations and exfiltrating. [1]

What was done

  • The issue has been fixed in n8n versions 1.123.55, 2.25.7, and 2.26.1. [1]
  • Users should upgrade to one of these versions or later to remediate the vulnerability. [1]

Sources

  1. GHSA-rm2v-h48j-895m — GitHub Advisory Database

Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.

Share advisory brief with your team

Copy a plain-text summary for Slack, GitHub issues, or team security channels.

Brief
[CVE-2026-54304] n8n: SecurityScorecard Node Leaks API Token to User-Controlled Host
Product: n8n | Affected: npm/n8n < 1.123.55; npm/n8n >= 2.0.0-rc.0, < 2.25.7; npm/n8n >= 2.26.0, < 2.26.1 | Fixed in: 1.123.55, 2.25.7, 2.26.1
Summary: An authenticated user with permission to create or modify workflows and access to a SecurityScorecard credential with limited allowed domains could configure the SecurityScorecard node's report download operation to target an attacker-controlled URL.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/06/cve-2026-54304-n8n
Was this page useful?

Corrections

Report an error or request a correction. We review requests within 5 business days and add a dated correction note.

10 to 2,000 characters. A link to a source helps. Stored as plain text.

Discussions for CVE-2026-54304

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Check before you install

Paste a package name or a GitHub link and get a clear answer in seconds: Block, Review or No known issues. No account needed.

Check a package

Questions? Contact us