dbcve.org
CoderApplication

CVE-2026-55432

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 2.29.17 / 2.32.7 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available 6 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. Prior to versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2, the `CreateSubAgent` RPC did not validate a requested app sharing level against the template's `MaxPortSharingLevel` before persisting workspace apps, letting a workspace owner exceed the administrator's configured maximum. Exploitation requires the ability to register sub-agent apps in a workspace the attacker controls. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2clamps the sub-agent app sharing level to the template's `MaxPortSharingLevel`. As a workaround, disable wildcard app hostnames (`CODER_WILDCARD_ACCESS_URL`) to block subdomain-based app routing.

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
How this class of weakness works · CWE-862

The application checks who you are but not whether you're allowed to perform a given action, so any authenticated user can reach things meant for others. This is the classic “change the ID in the URL” bug. The fix is an authorization check on every request, evaluated against the acting user's permissions.

General guidance for the missing authorization class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.29.17>= 2.30.0, < 2.32.7>= 2.33.0, < 2.33.8>= 2.34.0, < 2.34.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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.29.17 / 2.32.7 / 2.33.8 or later
Fixed in 2.29.172.32.72.33.8
Vendor patch github.com →
Recommended fix High confidence

Upgrade to version 2.34.2 (latest fixed release), or to the appropriate fixed version for your branch: 2.29.7, 2.32.7, 2.33.8, or 2.34.2

  1. 1. Determine your current Coder version by checking the Coder dashboard or running `coder version`
  2. 2. Identify which version branch you are on (2.29.x, 2.30.x-2.32.x, 2.33.x, or 2.34.x)
  3. 3. For version 2.29.x: Upgrade to version 2.29.7 or later
  4. 4. For version 2.30.x-2.32.x: Upgrade to version 2.32.7 or later
  5. 5. For version 2.33.x: Upgrade to version 2.33.8 or later
  6. 6. For version 2.34.x: Upgrade to version 2.34.2 or later
  7. 7. If upgrading across major version branches, review the Coder changelog for any additional migration steps
  8. 8. After upgrade, verify the fix by testing that sub-agent app sharing levels are properly clamped to the template's MaxPortSharingLevel
Caveat Review Coder release notes for any breaking changes between your current version and the target version, especially when crossing major version boundaries

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55432 — 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-55432 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