Advisory

GHSA-f962-qm93-mj4c

Also known as: CVE-2026-55079, GO-2026-5911

Summary

Coder's unbounded memory allocation in provisioner file upload allows authenticated denial of service

Details

Summary

NewDataBuilder in provisionersdk/proto/dataupload.go allocated a byte slice using the client-supplied FileSize from a DataUpload message without an upper-bound check. Although the DRPC wire limit is 4 MiB, the FileSize value itself was unconstrained

Impact

An authenticated user able to reach the provisioner daemon serve endpoint could send a roughly 50-byte message declaring a huge FileSize (for example 1 TiB), triggering an unrecoverable Go out-of-memory abort that terminates coderd. This is a single-message denial of service affecting the entire deployment.

Patches

The fix validates FileSize against an upper bound (MaxFileSize = 100 MiB) before allocation.

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 access to the provisioner daemon serve endpoint to trusted provisioner daemon service accounts.

Resources

  • Fix: #25710

Credits

Coder would like to thank Anthropic's Security Team (ANT-2026-22442) for independently disclosing this issue!

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-07-06 20:54 UTC
Modified
2026-07-07 16:11 UTC

Affected packages and fixes

github.com/coder/coder/v2

Go · All systems

Affected

  • introduced 2.34.0, fixed 2.34.2 (semver)

Fixed versions

2.34.2

Fix

github.com/coder/coder/v2

Go · All systems

Affected

  • introduced 2.33.0, fixed 2.33.8 (semver)

Fixed versions

2.33.8

Fix

github.com/coder/coder/v2

Go · All systems

Affected

  • introduced 2.30.0, fixed 2.32.7 (semver)

Fixed versions

2.32.7

Fix

github.com/coder/coder/v2

Go · All systems

Affected

  • introduced 2.24.0, fixed 2.29.17 (semver)

Fixed versions

2.29.17

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences