CVE-2026-54309

Description

## Impact 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`). The default transport is stdio, which is not affected. ## Patches The issue has been fixed in n8n versions 2.25.7, and 2.26.2. 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: - Avoid running `@n8n/mcp-browser` with the HTTP transport; use the default stdio transport instead. - If HTTP transport is required, restrict network access to the listening port to trusted clients only using host-based firewall rules. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

How to fix CVE-2026-54309

To remediate CVE-2026-54309, upgrade the affected package to a fixed version below.

• —upgrade to 2.26.2 or later

Is CVE-2026-54309 being exploited?

No exploitation signal available. Neither CISA KEV nor a current EPSS score has been published for CVE-2026-54309.

Affected packages (1)

• >= 2.26.0, < 2.26.2

CVSS scores

References (2)

• PATCHgithub.com/n8n-io/n8n
• WEBgithub.com/n8n-io/n8n/security/advisories/GHSA-qrx8-25qr-5r7v