Coder up to 2.33.2 Azure Identity azureidentity.Validate vmId certificate validation

Summaryinfo

A vulnerability was found in Coder up to 2.33.2. It has been rated as problematic. Affected is the function azureidentity.Validate of the component Azure Identity. This manipulation of the argument vmId causes certificate validation. This vulnerability is registered as CVE-2026-46354. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability classified as problematic was found in Coder up to 2.33.2. Affected by this vulnerability is the function azureidentity.Validate of the component Azure Identity. The manipulation of the argument vmId with an unknown input leads to a certificate validation vulnerability. The CWE definition for the vulnerability is CWE-295. The product does not validate, or incorrectly validates, a certificate. As an impact it is known to affect integrity. The summary by CVE is:

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`.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-46354 since 05/13/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1587.003 for this issue.

Upgrading to version 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2 or 2.33.3 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• Coder

Version

• 2.24.0
• 2.24.1
• 2.24.2
• 2.24.3
• 2.24.4
• 2.29.0
• 2.29.1
• 2.29.2
• 2.29.3
• 2.29.4
• 2.29.5
• 2.29.6
• 2.29.7
• 2.29.8
• 2.29.9
• 2.29.10
• 2.29.11
• 2.29.12
• 2.30.0
• 2.30.1
• 2.30.2
• 2.30.3
• 2.30.4
• 2.30.5
• 2.30.6
• 2.30.7
• 2.31.0
• 2.31.1
• 2.31.2
• 2.31.3
• 2.31.4
• 2.31.5
• 2.31.6
• 2.31.7
• 2.31.8
• 2.31.9
• 2.31.10
• 2.31.11
• 2.32.0
• 2.32.1
• 2.33.0
• 2.33.1
• 2.33.2

Website

• Product: https://github.com/coder/coder/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion