{"document":{"category":"csaf_vex","csaf_version":"2.0","title":"CVE-2026-54304: n8n: SecurityScorecard Node Leaks API Token to User-Controlled Host","publisher":{"category":"vendor","name":"HarborGuard Database","namespace":"https://database.harborguard.co"},"tracking":{"id":"CVE-2026-54304","status":"final","version":"1","initial_release_date":"2026-06-23T15:48:44.518Z","current_release_date":"2026-06-23T17:18:31.381Z","revision_history":[{"date":"2026-06-23T15:48:44.518Z","number":"1","summary":"Initial machine-readable export from HarborGuard."}]},"distribution":{"tlp":{"label":"WHITE"},"text":"Public CVE data; freely redistributable."},"notes":[{"category":"description","text":"n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.1, 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. This vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.1.","title":"CVE description"}],"references":[{"category":"self","summary":"CVE-2026-54304 on HarborGuard Database","url":"https://database.harborguard.co/cve/CVE-2026-54304"},{"category":"external","summary":"CVE Record","url":"https://www.cve.org/CVERecord?id=CVE-2026-54304"},{"category":"external","summary":"https://github.com/n8n-io/n8n/security/advisories/GHSA-rm2v-h48j-895m","url":"https://github.com/n8n-io/n8n/security/advisories/GHSA-rm2v-h48j-895m"}]},"product_tree":{"branches":[{"category":"vendor","name":"n8n-io","branches":[{"category":"product_name","name":"n8n","branches":[{"category":"product_version","name":"< 1.123.55","product":{"name":"n8n-io n8n < 1.123.55","product_id":"CSAFPID-1","product_identification_helper":{"cpe":"cpe:2.3:a:n8n-io:n8n:*:*:*:*:*:*:*:*"}}},{"category":"product_version","name":">= 2.26.0, < 2.26.1","product":{"name":"n8n-io n8n >= 2.26.0, < 2.26.1","product_id":"CSAFPID-2","product_identification_helper":{"cpe":"cpe:2.3:a:n8n-io:n8n:*:*:*:*:*:*:*:*"}}},{"category":"product_version","name":">= 2.0.0-rc.0, < 2.25.7","product":{"name":"n8n-io n8n >= 2.0.0-rc.0, < 2.25.7","product_id":"CSAFPID-3","product_identification_helper":{"cpe":"cpe:2.3:a:n8n-io:n8n:*:*:*:*:*:*:*:*"}}}]}]}]},"vulnerabilities":[{"cve":"CVE-2026-54304","title":"n8n: SecurityScorecard Node Leaks API Token to User-Controlled Host","notes":[{"category":"description","text":"n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.1, 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. This vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.1.","title":"CVE description"}],"product_status":{"known_affected":["CSAFPID-1","CSAFPID-2","CSAFPID-3"]},"scores":[{"cvss_v4":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:N","baseScore":7.1,"baseSeverity":"HIGH"},"products":["CSAFPID-1","CSAFPID-2","CSAFPID-3"]}],"remediations":[{"category":"none_available","details":"No fixed version is published yet. Monitor the upstream advisory.","product_ids":["CSAFPID-1","CSAFPID-2","CSAFPID-3"]}]}]}