The vulnerability exists because the MCP browser's HTTP transport mode did not require any authentication, allowing unauthenticated access to browser-control capabilities. The analysis of the patch commit reveals that the main function in packages/@n8n/mcp-browser/src/server.ts was responsible for creating an HTTP server with a request handler that lacked any authentication checks. This handler, an anonymous function within createServer, would process any incoming request, making it the vulnerable component. The fix involved a significant refactoring of this file, introducing a new startHttpTransport function that incorporates an authentication check using the newly added isAuthorized function. This function enforces bearer token authentication for all incoming requests to the MCP endpoint. Therefore, the main function (and its anonymous request handler) is identified as the vulnerable function, as it was the entry point for unauthenticated requests in the vulnerable versions.