Advisory

GHSA-rm2v-h48j-895m

Also known as: CVE-2026-54304

Summary

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

Details

Impact
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. The node attached the SecurityScorecard API token to the outbound request, causing the credential to be sent to the attacker-controlled host bypassing credential configured limitations and exfiltrating.

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

Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

  • Limit workflow creation and editing permissions to fully trusted users only.
  • Disable the SecurityScorecard node by adding n8n-nodes-base.securityScorecard to the NODES_EXCLUDE environment variable.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-06-16 23:34 UTC
Modified
2026-07-20 14:00 UTC

Affected packages and fixes

n8n

npm · All systems

Affected

  • introduced 0, fixed 1.123.55 (semver)

Fixed versions

1.123.55

Fix

n8n

npm · All systems

Affected

  • introduced 2.26.0, fixed 2.26.1 (semver)

Fixed versions

2.26.1

Fix

n8n

npm · All systems

Affected

  • introduced 2.0.0-rc.0, fixed 2.25.7 (semver)

Fixed versions

2.25.7

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences