Review reviewCritical

CVE-2026-46354

coder

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

CVSS
9.1
EPSS
0.26%
17.7% percentile
CISA KEV
Not listed
Published
2026.07.08
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.26%
Technical severityCVSS 9.1

Vulnerability overview

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

Affected product and versions

Product
coder
Affected versions
>= 2.33.0-rc.0, < 2.33.3, >= 2.32.0-rc.0, < 2.32.2, >= 2.31.0, < 2.31.12, >= 2.30.0, < 2.30.8, >= 2.29.0, < 2.29.13, < 2.24.5, >= 2.29.0 < 2.29.13, >= 2.30.0 < 2.30.8, >= 2.31.0 < 2.31.12, >= 2.32.0 < 2.32.2, >= 2.33.0 < 2.33.3
Fixed versions
2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, 2.33.3

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that coder and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CWE
CWE-347