The AI Bridge Proxy (aibridgeproxyd) in Coder's product created a goproxy server with a default transport configuration that set InsecureSkipVerify to true, effectively disabling TLS certificate verification for outbound HTTPS connections when no upstream proxy was configured. This means that in default setups, the proxy accepted any TLS certificate from the Coder access URL, exposing the connection to man-in-the-middle attacks. An attacker positioned on the network path between the proxy and the Coder server could intercept sensitive information such as Coder session tokens, user-supplied provider API keys, and full request and response bodies. The default transport also respected HTTP_PROXY and HTTPS_PROXY environment variables, allowing traffic redirection via environment manipulation. The vulnerability affects versions starting from 2.30.0 up to but excluding 2.32.7, 2.33.8, and 2.34.2, where the issue is fixed by applying secure TLS transport (TLS 1.2 or higher with system root CAs) unconditionally. Earlier versions before 2.30.0 are not affected as the AI Bridge Proxy was introduced in 2.30.0. Workarounds include ensuring trusted certificates on the Coder access URL and securing the network path between the proxy and server, for example by using loopback or mTLS.

An attacker with network position between the AI Bridge Proxy and the Coder server can intercept and potentially manipulate sensitive data including session tokens, API keys, and request/response payloads due to the lack of TLS certificate verification in default configurations. This compromises confidentiality and integrity of communications. The vulnerability does not affect deployments where the proxy and server communicate over loopback or otherwise secured channels. There are no known exploits in the wild at this time.

A fix is available and has been released in versions 2.32.7, 2.33.8, and 2.34.2 of Coder. Users should upgrade to these or later versions to ensure TLS certificate verification is enforced unconditionally. Until patched, users should secure the network path between the AI Bridge Proxy and the Coder server, for example by using loopback interfaces or mutual TLS (mTLS), and ensure the Coder access URL uses a trusted TLS certificate. The vendor advisory confirms the fix and recommends these workarounds.