Unable to connect to hub at http://<IP>:4444/grid/register – Selenium Grid Hub

Selenium Grid 4 hubs bind to 0.0.0.0 by default, which allows the hub to be reachable from any network interface. While this facilitates node registration across different networks, it introduces a security gap because the hub lacks built-in authentication or authorization mechanisms.

In cloud-based deployments, this default behavior may inadvertently expose the test infrastructure to public networks. Currently, the documented approach to secure the hub relies on external layers such as firewalls or reverse proxies rather than native configuration parameters.

Given the lack of native identity management in the hub, how can operators ensure that only authorized nodes can register and submit sessions without introducing significant latency via a proxy? Is there a planned configuration for native authentication in upcoming releases?