Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45796 medium CVSS 6.5

SSRF (Server-Side Request Forgery) in github.com/coder/coder/v2 (CVE-2026-45796)

Summary

SSRF in github.com/coder/coder/v2 (CVE-2026-45796). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v2/workspaceagents/azure-instance-identity. Mitigation: upgrade to 2.24.5 or later.

Original description

The description as published by the source.

Coder allows organizations to provision remote development environments via Terraform. Versions prior tp 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3 are vulnerable to unauthenticated semi-blind Server-Side Request Forgery (SSRF) via the Azure instance identity endpoint (POST /api/v2/workspaceagents/azure-instance-identity). An external attacker can force the Coder server to issue HTTP GET requests to arbitrary internal or external hosts by submitting a crafted PKCS#7 signature. The server does not return the target's response body, but error messages in the API response reveal whether the target is reachable and what type of failure occurred. Versions 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3 patch the issue. As a workaround, if the Azure identity-auth mechanism is not being used then restrict access to the corresponding endpoint (/api/v2/workspaceagents/azure-instance-identity) using ingress firewall and/or proxy ACLs.

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-45796 has been found in github.com/coder/coder/v2.
Attackers can target a specific entry point like POST /api/v2/workspaceagents/azure-instance-identity over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade github.com/coder/coder/v2 to 2.24.5 or later.
If unsure, ask your IT team or search "github.com/coder/coder/v2 CVE-2026-45796" on the vendor's site.

CVE-2026-45796 (github.com/coder/coder/v2) — CWE-918 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v2/workspaceagents/azure-instance-identity / IssuingCertificateURL / http.DefaultClient / allowedSigners
Patched: 2.24.5 — apply immediately
Workaround: If the Azure identity-auth mechanism is not being used then restrict access to the corresponding endpoint (/api/v2/workspaceagents/azure-instance-identity) using ingress firewall and/or proxy ACLs.
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

SSRF (CWE-918) exists in github.com/coder/coder/v2. Attackers reach the vulnerable code path via POST /api/v2/workspaceagents/azure-instance-identity without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/coder/coder/v2. Attack surface: POST /api/v2/workspaceagents/azure-instance-identity / IssuingCertificateURL / http.DefaultClient / allowedSigners.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.24.5.

🛡️ Workaround

Workaround: If the Azure identity-auth mechanism is not being used then restrict access to the corresponding endpoint (/api/v2/workspaceagents/azure-instance-identity) using ingress firewall and/or proxy ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/v2/workspaceagents/azure-instance-identity 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 'POST /api/v2/workspaceagents/azure-instance-identity' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 3
    Apply temporary workaround mitigate 
    If the Azure identity-auth mechanism is not being used then restrict access to the corresponding endpoint (`/api/v2/workspaceagents/azure-instance-identity`) using ingress firewall and/or proxy ACLs.

    パッチが適用されるまでの応急処置として、If the Azure identity-auth mechanism is not being used then restrict access to the corresponding endpoint (/api/v2/workspaceagents/azure-instance-identity) using ingress firewall and/or proxy ACLs. を実施。回避策の副作用 (機能低下) を確認した上で。

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

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

  5. 5
    Post-deployment verification verify 
    Replay attack against POST /api/v2/workspaceagents/azure-instance-identity 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.24.5"}]}]
go github.com/coder/coder
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"0.27.3"}]}]

References

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