GHSA-qrwj-vh9x-gw5vHigh· 8.3▾ TwilightCoder's workspace agent API insecure redirect handling allowed cross-agent file read and write
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 45.7 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
agentConn.apiClient() used the default redirect behavior of http.Client while its custom transport dialed the host from the request URL as long as the port was the workspace agent HTTP API port (4). Agent tailnet IPs are deterministic from agent UUIDs, so a malicious workspace agent could return a redirect to another agent's tailnet IP and cause the control-plane client to send the follow-up workspace agent API request to the victim agent instead of the intended agent.
Redirects that preserve the method and body, such as HTTP 307 and 308, allow replay of write and process-start requests. HTTP 301, 302 and 303 redirects only convert POST requests to GET requests, so they are sufficient to demonstrate redirected reads but not write or command-execution primitives.
An authenticated user with a running workspace and control of a modified workspace agent can redirect workspace agent API requests made to their agent toward another online workspace agent reachable on the tailnet. If the attacker knows the victim agent UUID, they can derive the victim's tailnet IP and target the victim's file APIs to read or write files as the victim workspace user.
In affected versions that expose the workspace agent process API, the same primitive can be chained to command execution as the victim workspace user by writing a payload through the redirected file API and then redirecting a process-start request to execute it. This crosses workspace and tenant boundaries.
The fix disables automatic redirect following for workspace agent API clients and pins all workspace agent API dials to the intended agent's deterministic tailnet address. Requests whose URL host does not match the intended agent are rejected instead of being dialed.
The fix was backported to all supported release lines:
None. Upgrading is required.
github.com/coder/coder/v2 >= 2.34.0, < 2.34.4github.com/coder/coder/v2 >= 2.33.0, < 2.33.10github.com/coder/coder/v2 >= 2.30.0, < 2.32.9github.com/coder/coder/v2 >= 2.27.0, < 2.29.19Upgrade to a patched release:
github.com/coder/coder/v2 2.34.4github.com/coder/coder/v2 2.33.10github.com/coder/coder/v2 2.32.9github.com/coder/coder/v2 2.29.19Connected by shared product, vendor, weakness, or advisory.
CVE-2026-63443High· 8.3Coder allows organizations to provision remote development environments via Terraform
GO-2026-5923NoneCoder's workspace agent API insecure redirect handling allowed cross-agent file read and write in github.com/coder/coder
CVE-2026-55428High· 8.2Coder: Route hijacking through lack of validation of agent-supplied AllowedIPs in tailnet coordinator
CVE-2026-55435Medium· 5.4Suspended Coder users retain access to AI Bridge LLM proxy endpoints
CVE-2024-27918High· 8.2Coder's OIDC authentication allows email with partially matching domain to register
GHSA-8fxq-53rx-ph5fLow· 3.7Coder: Login endpoint user enumeration via timing-defense placeholder in password comparison