INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-54304

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

CVE-2026-54304 ยท 2026-06-16 high

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Data exfiltration
Affected
n8n (npm)
Gets past
Sandbox or allowlist
CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
0.4% chance of exploitation in 30 days

How it works, in short

A workflow author points the SecurityScorecard report download at an attacker host, and the node sends the stored API token there despite the configured domain limits. (Our summary, written by a model. The source text is below.)

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.

References

Source: GitHub Advisory Database, used under CC BY 4.0.