Coder allows organizations to provision remote development environments via Terraform. In versions prior tp 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3, azureidentity.Validate() verifies that the PKCS#7 signer certificate chains to a trusted Azure CA but never verifies the PKCS#7 signature itself. An attacker can embed a legitimate Azure certificate alongside arbitrary content e.g. {"vmId":"<target>"} and the forged vmId will be accepted returning the victim workspace agent's session token. No authentication is required. The attacker only needs to know a target VM's vmId which is a UUIDv4. That's a practical limitation which would typically require prior access to be exploited. Versions 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3 patch the issue. As a workaround, reconfigure any Azure templates to use token authentication rather than azure-instance-identity.
{
"cwe_ids": [
"CWE-347"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46354.json",
"cna_assigner": "GitHub_M"
}{
"cpe": "cpe:2.3:a:coder:coder:*:*:*:*:*:go:*:*",
"source": [
"CPE_RANGE",
"REFERENCES"
],
"extracted_events": [
{
"introduced": "0"
},
{
"fixed": "2.24.5"
},
{
"introduced": "2.29.0"
},
{
"fixed": "2.29.13"
},
{
"introduced": "2.30.0"
},
{
"fixed": "2.30.8"
},
{
"introduced": "2.31.0"
},
{
"fixed": "2.31.12"
},
{
"introduced": "2.32.0"
},
{
"fixed": "2.32.2"
},
{
"introduced": "2.33.0"
},
{
"fixed": "2.33.3"
}
]
}