Vulnerability in github.com/coder/coder/v2 (CVE-2026-111933)
Summary
Vulnerability in github.com/coder/coder/v2 (CVE-2026-111933). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.29.17, 2.32.7, 2.33.8, 2.34.2 or later.
Original description
The description as published by the source.
Coder: Login endpoint user enumeration via timing-defense placeholder in password comparison in github.com/coder/coder
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-111933 has been found in github.com/coder/coder/v2.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade github.com/coder/coder/v2 to 2.29.17, 2.32.7, 2.33.8, 2.34.2 or later.
If unsure, ask your IT team or search "github.com/coder/coder/v2 CVE-2026-111933" on the vendor's site.
CVE-2026-111933 (github.com/coder/coder/v2) — CWE-203 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.29.17, 2.32.7, 2.33.8, 2.34.2 — apply immediately
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.
A vulnerability (CWE-203) exists in github.com/coder/coder/v2.
Check the vendor advisory for the affected versions of github.com/coder/coder/v2.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 2.29.17, 2.32.7, 2.33.8, 2.34.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/coder/coder/v2 to 2.29.17, 2.32.7, 2.33.8, 2.34.2ステージング環境で 2.29.17, 2.32.7, 2.33.8, 2.34.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com