← Back
CVE-2026-55079
medium
CVSS 4.9
Vulnerability in github.com/coder/coder/v2 (CVE-2026-55079)
Summary
vulnerability in github.com/coder/coder/v2 (CVE-2026-55079). Risk of unauthorized operations or information disclosure. Exploitable via ``NewDataBuilder``. Mitigation: upgrade to `2.29.17` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55079** has been found in github.com/coder/coder/v2.
Attackers can target a specific entry point like ``NewDataBuilder`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.9/10.
What to do: upgrade github.com/coder/coder/v2 to **2.29.17** or later.
If unsure, ask your IT team or search "github.com/coder/coder/v2 CVE-2026-55079" on the vendor's site.
CVE-2026-55079 (github.com/coder/coder/v2) — CWE-789 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `NewDataBuilder` / `FileSize` / `DataUpload` / `coderd`
Patched: `2.29.17` — apply immediately
Workaround: Restrict access to the provisioner daemon serve endpoint to trusted provisioner daemon service accounts.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-789) exists in github.com/coder/coder/v2. Attackers reach the vulnerable code path via ``NewDataBuilder`` without authentication.
📍 Affected scope
github.com/coder/coder/v2 — . Attack surface: `NewDataBuilder` / `FileSize` / `DataUpload` / `coderd`.
🔥 Severity
Severity: Medium (CVSS 4.9/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.29.17**.
🛡️ Workaround
Workaround: Restrict access to the provisioner daemon serve endpoint to trusted provisioner daemon service accounts.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/coder/coder/v2' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/coder/coder/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/coder/coder/v2` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Restrict access to the provisioner daemon serve endpoint to trusted provisioner daemon service accounts.パッチが適用されるまでの応急処置として、Restrict access to the provisioner daemon serve endpoint to trusted provisioner daemon service accounts. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade github.com/coder/coder/v2 to 2.29.17ステージング環境で 2.29.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/coder/coder/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.17"}]}]
References
- patch [email protected]
- patch [email protected]
- web https://github.com/advisories/GHSA-f962-qm93-mj4c
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]