Coder allows organizations to provision remote development environments via Terraform. In versions before 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3, the azureidentity.Validate() method verifies that a PKCS#7 signer's certificate chains to a trusted Azure CA but does not verify the PKCS#7 signature itself. An attacker can embed a legitimate Azure certificate with arbitrary payload, such as {"vmId":"<target>"}, causing the forged vmId to be accepted and returning the victim workspace agent's session token. No authentication is required; the attacker only needs to know a target VM’s vmId, a UUIDv4, which typically requires prior access. The issue is fixed in the listed patched releases, and a temporary workaround is to reconfigure Azure templates to use token authentication instead of azure-instance-identity.

All Coder releases prior to the patched versions 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3 are affected. The vulnerability specifically impacts the Azure instance identity feature used during Terraform provisioning; any environment that relies on this integration while running an affected Coder version is at risk.

The CVSS score of 9.1 highlights the high severity of unauthenticated token theft with remote impact. Because the vulnerability does not require user interaction or authentication, an attacker who knows a legitimate VM UUIDv4 can craft a malicious PKCS#7 payload from any network location. The EPSS score of < 1% indicates that, despite the high impact, the current probability of exploitation remains low, possibly requiring the attacker to already have some level of access or to discover a valid UUIDv4. The flaw is not listed in the CISA KEV catalog. Administrators should treat it as a critical risk until the affected releases are updated.