Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55077 high CVSS 7.2

Vulnerability in github.com/coder/coder/v2 (CVE-2026-55077)

Summary

Vulnerability in github.com/coder/coder/v2 (CVE-2026-55077). Successful exploitation can lead to full system takeover. Exploitable via PUT /api/v2/users/{user}/password. Mitigation: upgrade to 2.29.17 or later.

Original description

The description as published by the source.

Summary

The PUT /api/v2/users/{user}/password endpoint authorized only ActionUpdatePersonal and did not prevent a user-admin from resetting an owner account's password. It also did not require the current password when an admin reset another user's password.

Note: Exploitation requires the privileged user-admin role so practical risk is limited to deployments that grant user-admin to less trusted operators.

Impact

A user-admin could reset any owner's password without knowing it, authenticate as that owner and gain full deployment control, including templates, workspaces, licensing, organization settings and the ability to self-assign the owner role. This was a privilege escalation from user-admin to owner.

Patches

The fix prevents non-owner users from resetting the password of an account that holds the owner role.

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 the user-admin role to trusted administrators until upgrading.

Resources

  • Fix: #25709

Credits

Coder would like to thank Anthropic's Security Team (ANT-2026-22436) for independently…

Source: GitHub Security Advisories (Global) 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-55077 has been found in github.com/coder/coder/v2.
Attackers can target a specific entry point like PUT /api/v2/users/{user}/password over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/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-55077" on the vendor's site.

CVE-2026-55077 (github.com/coder/coder/v2) — CWE-285 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /api/v2/users/{user}/password / ActionUpdatePersonal / owner
Patched: 2.29.17 — apply immediately
Workaround: Restrict the user-admin role to trusted administrators until upgrading.
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-285) exists in github.com/coder/coder/v2. Attackers reach the vulnerable code path via PUT /api/v2/users/{user}/password.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/coder/coder/v2. Attack surface: PUT /api/v2/users/{user}/password / ActionUpdatePersonal / owner.

🔥 Severity

Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.29.17.

🛡️ Workaround

Workaround: Restrict the user-admin role to trusted administrators until upgrading.

🔍 Detection

Search webserver/proxy logs for unusual PUT /api/v2/users/{user}/password requests with malformed payloads or SQL meta-characters. 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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'PUT /api/v2/users/{user}/password' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで PUT /api/v2/users/{user}/password への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply temporary workaround mitigate 
    Restrict the `user-admin` role to trusted administrators until upgrading.

    パッチが適用されるまでの応急処置として、Restrict the user-admin role to trusted administrators until upgrading. を実施。回避策の副作用 (機能低下) を確認した上で。

  4. 4
    Apply patch patch 
    Upgrade github.com/coder/coder/v2 to 2.29.17

    ステージング環境で 2.29.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  5. 5
    Post-deployment verification verify 
    Replay attack against PUT /api/v2/users/{user}/password on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/coder/coder/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.29.17"}]}]
Go github.com/coder/coder
[{"type":"SEMVER","events":[{"introduced":"0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details