github.com/coder/coder/v2
Affected
- introduced
2.34.0, fixed2.34.2(semver)
Fixed versions
2.34.2
Fix
- Fixed version
2.34.2go get github.com/coder/coder/[email protected]
Advisory
Also known as: CVE-2026-55078, GO-2026-5916
Coder: Zip upload decompression lacks aggregate size limit, enabling denial of service
Summary
POST /api/v2/files converts zip uploads to tar in memory via CreateTarFromZip, which enforced a per-entry size limit but no aggregate limit on total decompressed output, writing to an unbounded in-memory buffer.
> Note: Exploitation requires authenticated file-upload access and the impact is limited to availability (denial of service).
Impact
An authenticated user could upload a zip within the 100 MiB upload limit but containing many highly compressible entries whose decompressed size exhausted memory, crashing coderd before any RBAC check. Repeated requests could keep the service unavailable. This is a denial of service; it does not allow data disclosure or code execution.
Patches
The fix adds a metadata preflight check that sums projected entry sizes and a streaming writer that enforces the aggregate limit during decompression.
The fix was backported to all supported release lines:
| Release line | Patched version |
|---|---|
| 2.34 | v2.34.2 |
| 2.33 | v2.33.8 |
| 2.32 | v2.32.7 |
| 2.29 (ESR) | v2.29.17 |
Workarounds
Restrict file-upload permissions to trusted users or place a reverse proxy with request-body size limits in front of coderd.
Resources
Credits
Coder would like to thank Anthropic's Security Team (ANT-2026-22438) for independently disclosing this issue!
Medium Basis: The source's own band: MODERATE
2.34.0, fixed 2.34.2 (semver)2.34.2
2.34.2go get github.com/coder/coder/[email protected]2.33.0, fixed 2.33.8 (semver)2.33.8
2.33.8go get github.com/coder/coder/[email protected]2.30.0, fixed 2.32.7 (semver)2.32.7
2.32.7go get github.com/coder/coder/[email protected]2.17.0, fixed 2.29.17 (semver)2.29.17
2.29.17go get github.com/coder/coder/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0