CVE-2026-54304

Description

## 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.

How to fix CVE-2026-54304

To remediate CVE-2026-54304, upgrade the affected package to a fixed version below.

• —upgrade to 1.123.55 or later

Is CVE-2026-54304 being exploited?

No exploitation signal available. Neither CISA KEV nor a current EPSS score has been published for CVE-2026-54304.

Affected packages (1)

• from 0, < 1.123.55

CVSS scores

References (2)

• PATCHgithub.com/n8n-io/n8n
• WEBgithub.com/n8n-io/n8n/security/advisories/GHSA-rm2v-h48j-895m