GHSA-jqj2-x4c5-jfxm: Coder: Devcontainer recreate endpoint missing write authorization allows read-only roles to destroy containers
A vulnerability in Coder's devcontainer recreate endpoint allows users with read-only workspace access to trigger destructive container rebuilds without proper write authorization. This authorization bypass can lead to data loss and denial of service by destroying uncommitted in-container state. The issue affects multiple release lines prior to patched versions. An explicit update authorization check has been added in fixed releases to prevent exploitation.
AI Analysis
Technical Summary
The devcontainer recreate endpoint in Coder's software relied on middleware that only checked read permissions (ActionRead) on the workspace, unlike the delete endpoint which also checked update permissions (ActionUpdate). This allowed any authenticated user with read-only access to recreate (and thus destroy) devcontainers, causing loss of uncommitted data and potential denial of service through repeated calls. The vulnerability requires an existing low-privilege role with access to the workspace. The fix introduces an explicit ActionUpdate authorization check before the destructive operation is performed. The fix has been backported to all supported release lines, including versions 2.34.2, 2.33.8, 2.32.7, and 2.29.17.
Potential Impact
Authenticated users with read-only workspace access can bypass intended authorization controls to destroy devcontainers, resulting in loss of uncommitted data and potential denial of service. This represents an authorization bypass vulnerability leading to integrity and availability impacts but does not affect confidentiality.
Mitigation Recommendations
A fix is available and has been backported to all supported release lines. Users should upgrade to versions 2.34.2, 2.33.8, 2.32.7, or 2.29.17 or later to remediate this vulnerability. No workarounds exist. Applying the official update is the recommended mitigation.
GHSA-jqj2-x4c5-jfxm: Coder: Devcontainer recreate endpoint missing write authorization allows read-only roles to destroy containers
Description
A vulnerability in Coder's devcontainer recreate endpoint allows users with read-only workspace access to trigger destructive container rebuilds without proper write authorization. This authorization bypass can lead to data loss and denial of service by destroying uncommitted in-container state. The issue affects multiple release lines prior to patched versions. An explicit update authorization check has been added in fixed releases to prevent exploitation.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The devcontainer recreate endpoint in Coder's software relied on middleware that only checked read permissions (ActionRead) on the workspace, unlike the delete endpoint which also checked update permissions (ActionUpdate). This allowed any authenticated user with read-only access to recreate (and thus destroy) devcontainers, causing loss of uncommitted data and potential denial of service through repeated calls. The vulnerability requires an existing low-privilege role with access to the workspace. The fix introduces an explicit ActionUpdate authorization check before the destructive operation is performed. The fix has been backported to all supported release lines, including versions 2.34.2, 2.33.8, 2.32.7, and 2.29.17.
Potential Impact
Authenticated users with read-only workspace access can bypass intended authorization controls to destroy devcontainers, resulting in loss of uncommitted data and potential denial of service. This represents an authorization bypass vulnerability leading to integrity and availability impacts but does not affect confidentiality.
Mitigation Recommendations
A fix is available and has been backported to all supported release lines. Users should upgrade to versions 2.34.2, 2.33.8, 2.32.7, or 2.29.17 or later to remediate this vulnerability. No workarounds exist. Applying the official update is the recommended mitigation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jqj2-x4c5-jfxm
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-55433"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a4c340327e9c797195f5f2c
Added to database: 07/06/2026, 23:02:27 UTC
Last enriched: 07/06/2026, 23:12:05 UTC
Last updated: 07/07/2026, 03:25:17 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.