dbcve.org
CoderApplication

CVE-2026-46354

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-07
Fix available
A fix is available. Upgrade to 2.24.5 / 2.29.13 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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`.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Coder's azureidentity.Validate() function verifies that PKCS#7 signer certificates chain to a trusted Azure CA but fails to verify the signature itself. Attackers can embed a legitimate Azure certificate with forged content like {"vmId":"<target>"} to obtain victim workspace agent session tokens without authentication, requiring only knowledge of the target VM's UUIDv4.

MitigationUpgrade Coder to versions 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, or 2.33.3 and later, or reconfigure Azure templates to use token authentication instead of azure-instance-identity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CoderApplication
Affected:< 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

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Coder deployment version
    Run 'coder version' from the Coder server CLI or check the Helm chart/app version if using Kubernetes deployment
    Affected if The installed version falls within any of these ranges: < 2.24.5, >= 2.29.0 and < 2.29.13, >= 2.30.0 and < 2.30.8, >= 2.31.0 and < 2.31.12, >= 2.32.0 and < 2.32.2, >= 2.33.0 and < 2.33.3
  2. Locate Azure-based workspace templates
    List all templates via 'coder template list' and identify any using Azure compute (check template Terraform files for 'azurerm' resources)
    Affected if Azure-based templates exist in the Coder deployment
  3. Check Azure template authentication method
    Examine the template's Terraform configuration for the 'azure-instance-identity' authentication setting in the Coder provider block, typically the 'use_azure_instance_identity' or 'auth' parameter
    Affected if Templates configure Coder to authenticate using azure-instance-identity rather than token-based authentication

A deployment is affected if it runs a vulnerable Coder version AND uses Azure templates configured with azure-instance-identity authentication, allowing attackers with knowledge of Azure VM UUIDs to forge authentication tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.24.5 / 2.29.13 / 2.30.8 or later
Fixed in 2.24.52.29.132.30.8
Vendor patch github.com →
Interim mitigation

Upgrade Coder to versions 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, or 2.33.3 and later, or reconfigure Azure templates to use token authentication instead of azure-instance-identity.

Recommended fix High confidence

Upgrade to 2.24.5, 2.29.13, 2.30.8, or 2.31.12 (depending on your current version branch)

  1. Upgrade to the fixed version appropriate for your current branch: If on < 2.24.5, upgrade to 2.24.5 or later. If on 2.29.x (>= 2.29.0, < 2.29.13), upgrade to 2.29.13. If on 2.30.x (>= 2.30.0, < 2.30.8), upgrade to 2.30.8. If on 2.31.x (>= 2.31.0, < 2.31.12), upgrade to 2.31.12.
  2. Alternatively, as an immediate workaround, reconfigure any Azure templates to use token authentication instead of azure-instance-identity.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Coder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46354 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46354 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data