Skip to content

CVE-2026-46354

Coder vulnerability

9.1 CRITICALEPSS 0.32%
  1. Published7 Jul 2026

Description

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

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Coder≥ 2.29.0 < 2.29.13 · ≥ 2.30.0 < 2.30.8 · ≥ 2.31.0 < 2.31.12 · ≥ 2.32.0 < 2.32.2

Frequently asked

Is CVE-2026-46354 being actively exploited?

CVE-2026-46354 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.32%.

How severe is CVE-2026-46354?

CVE-2026-46354 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.32% probability of exploitation.

Which products are affected by CVE-2026-46354?

Affected products include Coder.

How do I fix CVE-2026-46354?

Upgrade affected software to a fixed version, for example Coder 2.29.13 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-46354 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.