CVE-2026-55429 coder vulnerability
Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2, `UpsertWorkspaceApp` overwrites an existing app's `agent_id` on a primary-key conflict and `insertAgentApp` accepts the app ID from the provisioner's `CompleteJob` payload without verifying it belongs to the workspace being built. `CompleteJob` runs under `dbauthz.AsProvisionerd` so the authorization layer does not block the cross-workspace upsert. Exploitation requires elevated access as a template author or external provisioner operator. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 verifies that any existing `workspace_apps` row matching the supplied ID belongs to the workspace being built and rejects cross-workspace agent reassignment. No known workarounds are available.
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
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-55429 affects Coder remote development deployments before the patched Coder releases. The practical risk is cross-workspace or agent authorization bypass that can affect workspace app ownership, tailnet routing, or peer access boundaries. Prioritize multi-tenant Coder deployments, external provisioner deployments, and environments with untrusted template authors or workspace owners. Coder fixed this issue in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2; deploy the matching patched branch or a later supported release. Where the advisory lists a workaround, apply it only as a temporary control until the patched version is deployed.
- Inventory all Coder server, CLI, provisioner, AI Bridge Proxy, workspace app proxy, and template-author deployments across production, staging, and developer environments.
- Identify affected Coder versions and compare each deployment against the fixed releases: 2.29.7, 2.32.7, 2.33.8, and 2.34.2, or a later supported release.
- Upgrade Coder servers and related components to the patched release for the installed branch, then roll out updated CLI binaries to users and automation hosts where the CLI is affected.
- Restrict template-author, external provisioner, and workspace-owner privileges to trusted users until patched.
- Review role bindings, template-author privileges, provisioner daemon access, wildcard app hostname exposure, and reverse proxy header handling for unnecessary trust.
- Review workspace app ownership changes, tailnet coordinator logs, AllowedIPs prefixes, and cross-workspace access anomalies.
- If exploitation or credential exposure is suspected, revoke affected sessions, rotate tokens and credentials, preserve audit logs, and rebuild affected workspaces or hosts where integrity cannot be trusted.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every Coder component reports a patched version: 2.29.7, 2.32.7, 2.33.8, and 2.34.2, or a later supported release for that branch.
- Confirm workspace app IDs, agent IDs, and AllowedIPs are validated against the authoritative workspace or agent identity.
- Validate proxy, wildcard app hostname, template, provisioner, and workspace permission settings against the intended least-privilege policy.
- Review Coder audit logs, reverse proxy logs, and workspace telemetry for exploitation attempts before and after patching.
- Document patched versions, changed settings, residual exceptions, and evidence, then rerun Fixnx or the relevant vulnerability scan where applicable.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-55429?
coder should be checked against the vendor advisory and trusted references linked on this page.
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.