NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · n8n

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

highCVSS 4.0 7.1 · 3.1 7.7GHSA-rm2v-h48j-895m

The n8n SecurityScorecard node's report download operation sends the SecurityScorecard API token to whatever URL the workflow author sets, even when the credential limits allowed domains. A workflow editor can steal the token by pointing the node at their own server. Fixed in n8n 1.123.55, 2.25.7 and 2.26.1.

Published Jun 16, 2026 · Updated Jul 20, 2026 · Analysis Oct 26, 2026

What an attacker can do

n8n credentials can carry an allowed-domains list, so an API token is only sent to approved hosts. The SecurityScorecard node's report download operation accepts a target URL and attaches the API token to the outbound request without honoring that restriction. The advisory does not name the code path.

The attacker is an authenticated user who can create or edit workflows and who can use a SecurityScorecard credential, though not necessarily read its value. They point the download operation at a server they run and read the token from the incoming Authorization header. The token is leaked to the attacker-controlled host, which defeats the domain limit the credential owner set (CWE-200). The scope is changed in CVSS 3.1 because the stolen token works against an outside service.

With the token, the attacker can query SecurityScorecard as your organization: ratings, reports and company data tied to your account. The workflow editor role is often given widely, so the practical risk is a colleague or compromised account turning use-only access into secret theft.

Who is affected

n8n on npm in these ranges: below 1.123.55; from 2.0.0-rc.0 below 2.25.7; and from 2.26.0 below 2.26.1. Only instances that use the SecurityScorecard node with a stored credential are at risk. Check:

npm ls n8n
n8n --version

Docker and cloud installs show the version in the n8n UI.

n8n

Ecosystem
npm
Affected
< 1.123.55
Fixed in
1.123.55
Check
npm ls n8n

n8n

Ecosystem
npm
Affected
>= 2.26.0, < 2.26.1
Fixed in
2.26.1
Check
npm ls n8n

n8n

Ecosystem
npm
Affected
>= 2.0.0-rc.0, < 2.25.7
Fixed in
2.25.7
Check
npm ls n8n

How to fix it

Upgrade to 1.123.55, 2.25.7 or 2.26.1, or later. Note that for the 2.26 line the fix is 2.26.1, not 2.26.2.

npm install -g n8n@latest

For Docker, pull a newer n8nio/n8n image. Temporary mitigations from the advisory, which do not fully remove the risk: limit workflow creation and editing to fully trusted users, and disable the node by adding n8n-nodes-base.securityScorecard to the NODES_EXCLUDE environment variable. After upgrading, rotate any SecurityScorecard token that untrusted editors could have used.

How to tell if you were hit

The advisory lists no indicators. Review workflows that contain a SecurityScorecard node with the report download operation and check whether the URL points at a host other than the SecurityScorecard API. Look at workflow edit history for those nodes and at outbound request logs from the n8n host for unfamiliar destinations. In SecurityScorecard, review API activity for the token's usage from unfamiliar IP addresses.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to 34selen.

Questions

Does the attacker need to know the SecurityScorecard token?

No. They need workflow edit permission and the ability to use the credential. The node sends the token to their server, so they never have to read it from the credential store.

Which n8n versions fix CVE-2026-54304?

1.123.55, 2.25.7 and 2.26.1, or later. The 2.26 line is fixed in 2.26.1.

Do allowed-domain limits on the credential help?

Not on affected versions. The advisory says the leak bypasses the limits configured on the credential.

Is it exploited in the wild?

The sources do not report exploitation, and the entry has no CISA KEV data.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More n8n vulnerabilities

All n8n entries