VDB
KO
HIGH 7.7

GHSA-rm2v-h48j-895m

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.

Are you affected?

Enter the version of the package you're using.

Affected packages

npm / n8n
Introduced in: 0 Fixed in: 1.123.55
Fix npm install n8n@1.123.55
npm / n8n
Introduced in: 2.26.0 Fixed in: 2.26.1
Fix npm install n8n@2.26.1
npm / n8n
Introduced in: 2.0.0-rc.0 Fixed in: 2.25.7
Fix npm install n8n@2.25.7

References