n8n is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, when @n8n/mcp-browser is run in HTTP transport mode, the MCP endpoint accepts session initialization and tool invocation requests without any authentication. Any network-reachable client, or any website visited by the user, can establish an MCP session and invoke browser-control tools. Where the n8n AI Browser Bridge extension is installed and a browser connection is active, an unauthenticated caller can access browser-control capabilities including navigation, JavaScript evaluation, and cookie and storage access against the user's real browser profile. This issue only affects instances where @n8n/mcp-browser is run with the HTTP transport (--transport http). This vulnerability is fixed in 2.25.7 and 2.26.2.
CVE-2026-54309
This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 68% 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
- 10.0
- EG Score
- 10.0(medium)
- EPSS
- 32.3%
- KEV
- Not listed
Published
June 16, 2026
Last Modified
June 25, 2026
Advisory Details (1)
Auto-updated Jul 3, 2026n8n MCP Browser HTTP Transport Exposes Unauthenticated Browser-Control Sessions · Advisory · n8n-io/n8n · GitHub
https://github.com/n8n-io/n8n/security/advisories/GHSA-qrx8-25qr-5r7vVendor Advisories for CVE-2026-54309(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 44× in last 7d / 126× 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.
Showing the most recent 100 of 126 total refreshes for this CVE.
- 2026-07-07 09:58 UTCEG score recompute
- 2026-07-07 02:49 UTCEG score recompute
- 2026-07-06 22:56 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 04:06 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 00:16 UTCEG score recompute
- 2026-07-05 20:25 UTCEG score recompute
- 2026-07-05 16:35 UTCEG score recompute
- 2026-07-05 12:30 UTCEG score recompute
- 2026-07-05 08:39 UTCEG score recompute
- 2026-07-05 02:11 UTCEG score recompute
- 2026-07-04 22:20 UTCEG score recompute
- 2026-07-04 18:29 UTCEG score recompute
- 2026-07-04 12:49 UTCEG score recompute
- 2026-07-04 08:59 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 01:18 UTCEG score recompute
- 2026-07-03 21:23 UTCEG score recompute
- 2026-07-03 17:33 UTCEG score recompute
- 2026-07-03 13:43 UTCEG score recompute
- 2026-07-03 06:43 UTCEG score recompute
Show 75 moreShow fewer
- 2026-07-03 02:48 UTCEG score recompute
- 2026-07-02 22:57 UTCEG score recompute
- 2026-07-02 19:06 UTCEG score recompute
- 2026-07-02 15:13 UTCEG score recompute
- 2026-07-02 11:13 UTCEG score recompute
- 2026-07-02 07:14 UTCEG score recompute
- 2026-07-02 03:19 UTCEG score recompute
- 2026-07-01 23:29 UTCEG score recompute
- 2026-07-01 19:39 UTCEG score recompute
- 2026-07-01 15:49 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 11:57 UTCEG score recompute
- 2026-07-01 08:07 UTCEG score recompute
- 2026-07-01 04:16 UTCEG score recompute
- 2026-07-01 00:23 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 20:30 UTCEG score recompute
- 2026-06-30 16:40 UTCEG score recompute
- 2026-06-30 12:50 UTCEG score recompute
- 2026-06-30 08:56 UTCEG score recompute
- 2026-06-30 05:05 UTCEG score recompute
- 2026-06-30 01:14 UTCEG score recompute
- 2026-06-29 21:24 UTCEG score recompute
- 2026-06-29 17:34 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 13:30 UTCEG score recompute
- 2026-06-29 09:40 UTCEG score recompute
- 2026-06-29 05:43 UTCEG score recompute
- 2026-06-29 01:50 UTCEG score recompute
- 2026-06-28 21:59 UTCEG score recompute
- 2026-06-28 18:08 UTCEG score recompute
- 2026-06-28 14:16 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 10:25 UTCEG score recompute
- 2026-06-28 06:29 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 02:39 UTCEG score recompute
- 2026-06-27 22:49 UTCEG score recompute
- 2026-06-27 18:59 UTCEG score recompute
- 2026-06-27 15:09 UTCEG score recompute
- 2026-06-27 11:18 UTCEG score recompute
- 2026-06-27 07:28 UTCEG score recompute
- 2026-06-27 03:37 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 23:29 UTCEG score recompute
- 2026-06-26 19:39 UTCEG score recompute
- 2026-06-26 15:49 UTCEG score recompute
- 2026-06-26 11:49 UTCEG score recompute▲ 1.20
- 2026-06-25 19:49 UTCNVD updateCVSS v3 → 10 · severity → CRITICAL
- 2026-06-25 18:47 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 07:22 UTCEG score recompute
- 2026-06-24 19:55 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 06:41 UTCEG score recompute
- 2026-06-23 19:16 UTCEG score recompute▼ 1.20
- 2026-06-23 15:45 UTCMITRE cvelistV5CVSS v3 → 8.8 · CVSS v4 → 8.8
- 2026-06-23 15:22 UTCEG score recompute
- 2026-06-23 11:28 UTCEG score recompute
- 2026-06-23 07:28 UTCEG score recompute
- 2026-06-23 03:23 UTCEG score recompute
- 2026-06-22 23:24 UTCEG score recompute
- 2026-06-22 19:33 UTCEG score recompute
- 2026-06-22 15:41 UTCEG score recompute
- 2026-06-22 11:49 UTCEG score recompute
- 2026-06-22 07:56 UTCEG score recompute
- 2026-06-22 04:03 UTCEG score recompute
- 2026-06-22 00:11 UTCEG score recompute
- 2026-06-21 20:17 UTCEG score recompute
- 2026-06-21 16:25 UTCEG score recompute
- 2026-06-21 12:32 UTCEG score recompute
- 2026-06-21 08:38 UTCEG score recompute
- 2026-06-21 04:48 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-306
- CVE-2011-10013EG 10.0CRITICAL
- CVE-2014-125124EG 10.0CRITICAL
- CVE-2017-2637EG 10.0EPSS 91%CRITICAL
- CVE-2010-5326EG 10.0 KEVEPSS 97%CRITICAL
- CVE-2018-25134EG 9.8CRITICAL
- CVE-2012-10030EG 9.8CRITICAL
- CVE-2018-21132EG 9.8CRITICAL
- CVE-2014-3449EG 9.8CRITICAL
- CVE-2006-0062EG 9.8CRITICAL
- CVE-2006-0061EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-54309?
When was CVE-2026-54309 disclosed?
Is CVE-2026-54309 actively exploited?
What is the CVSS score of CVE-2026-54309?
How do I remediate CVE-2026-54309?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54309
Is Your Infrastructure Affected by CVE-2026-54309?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.