fixnx
criticalCVE-2026-46354

CVE-2026-46354 Coder vulnerability

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

ProductCoder
CVSS9.1
EPSS0.0026
UpdatedJuly 12, 2026

Quick answer

Coder should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • <2.24.5
  • <2.29.13
  • <2.30.8
  • <2.31.12
  • <2.32.2
  • <2.33.3

Fixed versions

  • 2.24.5
  • 2.29.13
  • 2.30.8
  • 2.31.12
  • 2.32.2
  • 2.33.3

How to fix it

CVE-2026-46354 affects Coder remote development deployments where Azure instance identity validation trusts the PKCS#7 signer certificate chain without verifying the PKCS#7 signature, allowing forged vmId content and workspace agent token theft. Prioritize internet-facing, shared, or multi-tenant Coder environments because compromise can affect developer workspaces, identity flows, tokens, or control-plane availability depending on the issue. Upgrade to Coder 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3, or a later supported release on the relevant branch, because those are the vendor-supported patched versions. Reconfigure Azure templates to use token authentication instead of azure-instance-identity until every Coder deployment is patched.

  1. Inventory all Coder servers, workspace proxies, provisioner daemons, AI Bridge components, templates, and CLI installations across production, staging, and developer environments.
  2. Identify affected Coder versions and compare every deployment with the fixed releases for CVE-2026-46354: 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3.
  3. Upgrade Coder servers and related components to the patched release for the installed branch, then roll updated CLI or automation binaries where they are part of the affected workflow.
  4. Reconfigure Azure templates to use token authentication instead of azure-instance-identity until every Coder deployment is patched.
  5. Review Coder role bindings, OIDC settings, API keys, template parameters, provisioner access, workspace app exposure, and reverse proxy rules for unnecessary trust or public reachability.
  6. Review Coder audit logs, reverse proxy logs, provisioner logs, and workspace events for suspicious requests matching the affected endpoint or workflow.
  7. If exploitation or credential exposure is suspected, revoke affected sessions, rotate API keys and workspace tokens, preserve audit evidence, and rebuild workspaces or hosts whose integrity cannot be trusted.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm every affected Coder component reports a patched version for CVE-2026-46354: 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3, or a later supported release.
  • Confirm PKCS#7 validation verifies the cryptographic signature, not only the signer certificate chain.
  • Confirm temporary restrictions, role changes, OIDC settings, proxy ACLs, and API-key revocations match the intended least-privilege policy.
  • Review logs after patching to confirm exploit attempts are blocked or fail safely without exposing credentials, internal network details, or control-plane availability.
  • Document patched versions, configuration changes, remaining exceptions, and evidence, then rerun Fixnx or the relevant vulnerability scan where applicable.

Related categories

Cloud SecurityDevOpsInformation DisclosureCryptography

Trusted references

Source advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVD

FAQ

What is affected by CVE-2026-46354?

Coder versions listed as affected should be reviewed: <2.24.5, <2.29.13, <2.30.8, <2.31.12, <2.32.2, <2.33.3.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.