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.
CVE-2026-54304
This high-severity CVE scores 7.7 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(medium)
- EPSS
- 27.4%
- KEV
- Not listed
Published
June 16, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 23, 2026SecurityScorecard Node Leaks API Token to User-Controlled Host · Advisory · n8n-io/n8n · GitHub
https://github.com/n8n-io/n8n/security/advisories/GHSA-rm2v-h48j-895mVendor Advisories for CVE-2026-54304(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| n8n | — | 2.25.7 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 60× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 22:55 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 01:28 UTCEG score recompute
- 2026-07-05 13:36 UTCEG score recompute
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 01:44 UTCEG score recompute
- 2026-07-04 13:46 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 01:54 UTCEG score recompute
- 2026-07-03 13:43 UTCEG score recompute
- 2026-07-02 23:39 UTCEG score recompute
- 2026-07-02 11:46 UTCEG score recompute
- 2026-07-01 23:43 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 11:50 UTCEG score recompute
- 2026-06-30 23:58 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 12:05 UTCEG score recompute
- 2026-06-29 22:53 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
Show 35 moreShow fewer
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 11:01 UTCEG score recompute
- 2026-06-28 23:09 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 11:17 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 23:25 UTCEG score recompute
- 2026-06-27 11:33 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 23:40 UTCEG score recompute
- 2026-06-26 11:48 UTCEG score recompute▲ 0.60
- 2026-06-26 03:53 UTCNVD updateCVSS v3 → 7.7
- 2026-06-25 22:09 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 10:14 UTCEG score recompute
- 2026-06-24 22:11 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 10:20 UTCEG score recompute
- 2026-06-23 22:13 UTCEG score recompute▼ 0.60
- 2026-06-23 17:34 UTCNVD updateCVSS v3 → 7.1 · CVSS v4 → 7.1
- 2026-06-23 10:16 UTCEG score recompute
- 2026-06-22 22:24 UTCEG score recompute
- 2026-06-22 10:32 UTCEG score recompute
- 2026-06-21 22:38 UTCEG score recompute
- 2026-06-21 10:45 UTCEG score recompute
- 2026-06-20 22:53 UTCEG score recompute
- 2026-06-20 10:58 UTCEG score recompute
- 2026-06-19 23:04 UTCEG score recompute
- 2026-06-19 11:11 UTCEG score recompute
- 2026-06-18 23:16 UTCEG score recompute
- 2026-06-18 11:21 UTCEG score recompute
- 2026-06-17 23:29 UTCEG score recompute
- 2026-06-17 11:36 UTCEG score recompute
- 2026-06-16 23:44 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-200
Frequently asked(5)
What is CVE-2026-54304?
When was CVE-2026-54304 disclosed?
Is CVE-2026-54304 actively exploited?
What is the CVSS score of CVE-2026-54304?
How do I remediate CVE-2026-54304?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54304
Is Your Infrastructure Affected by CVE-2026-54304?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.