Technical impact
Coder releases before 2.29.21, 2.34.12, 2.35.9, 2.36.7, and 2.37.4 do not validate the audience claim of GCE instance‑identity JSON Web Tokens presented to the /api/v2/workspaceagents/google-instance-identity endpoint, a flaw identified as CWE‑441. The server accepts any well‑formed token, allowing an attacker who obtains a valid identity token minted for a different relying party to replay that token and receive a workspace agent session token. That session remains active until the next workspace build, granting the attacker full control over the agent without legitimate credentials.
Affected Systems
All Coder installations with versions older than 2.29.21, 2.34.12, 2.35.9, 2.36.7, or 2.37.4 are impacted. The vendor is coder and the product is Coder. Administrators should verify that their deployments are running a patched release and plan remediation accordingly.
Risk and Exploitability
The CVSS score of 8.3 classifies this vulnerability as high severity. The EPSS score of 0.00186 indicates an exploitation probability of less than one percent, and the issue is not listed in CISA’s KEV catalog, which suggests that no public exploitation has been documented yet. Evidence from the description indicates that an attacker must possess an unexpired GCE instance‑identity JWT issued for a different relying party. Based on the description, it is inferred that such a token can be obtained by accessing a Google Cloud Compute instance or by abusing misconfigured IAM permissions. Replay of the token is trivial once acquired, and the resulting session token grants full control over the workspace agent until the next build, presenting a significant risk for privileged operations and potential lateral movement.