n8n: SecurityScorecard Node Leaks API Token to User-Controlled Host
CVE-2026-54304 · GHSA-rm2v-h48j-895m · published 2026-06-16 · updated 2026-07-20
- Severity
- High
- CVSS score
- 7.7
- Chance of exploitation (EPSS)
- 0.38%
- Fixed in
- 2.26.1
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
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.
Upgrade n8n to 2.26.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
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.
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.
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- HighWorkspace dotenv files could override provider credentialsopenclaw
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.