Categories
CVE-2026-55436 high CVSS 7.4

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

Summary

Vulnerability in github.com/coder/coder/v2 (CVE-2026-55436). Confidential information can be exposed externally. Exploitable via aibridgeproxyd. Mitigation: upgrade to 2.32.7 or later.

Original description

The description as published by the source.

Coder allows organizations to provision remote development environments via Terraform. Starting in version 2.30.0 and prior to versions 2.32.7, 2.33.8, and 2.34.2, the AI Bridge Proxy (aibridgeproxyd) created a goproxy server whose default transport set InsecureSkipVerify: true and only assigned a secure transport when an upstream proxy was configured. In the default configuration (no upstream proxy), outbound HTTPS to the Coder access URL accepted any TLS certificate. Practical exploitation requires an on-path (man-in-the-middle) position between the AI Bridge Proxy and the Coder server. Deployments where they are co-located over loopback are effectively unaffected. The fix in versions 2.32.7, 2.33.8, and 2.34.2 applies the secure transport (TLS 1.2 or higher using system root CAs) unconditionally. As a workaround, ensure the Coder access URL uses a trusted certificate and secure the network path between the AI Bridge Proxy and the Coder server (for example, loopback or mTLS).

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-55436 has been found in github.com/coder/coder/v2.
Attackers can target a specific entry point like aibridgeproxyd over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade github.com/coder/coder/v2 to 2.32.7 or later.
If unsure, ask your IT team or search "github.com/coder/coder/v2 CVE-2026-55436" on the vendor's site.

CVE-2026-55436 (github.com/coder/coder/v2) — CWE-295 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: aibridgeproxyd / HTTP_PROXY / HTTPS_PROXY
Patched: 2.32.7 — apply immediately
Workaround: Ensure the Coder access URL uses a trusted certificate and secure the network path between the AI Bridge Proxy and the Coder server (for example, loopback or mTLS).
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-295) exists in github.com/coder/coder/v2. Attackers reach the vulnerable code path via aibridgeproxyd without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/coder/coder/v2. Attack surface: aibridgeproxyd / HTTP_PROXY / HTTPS_PROXY.

🔥 Severity

Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.32.7.

🛡️ Workaround

Workaround: Ensure the Coder access URL uses a trusted certificate and secure the network path between the AI Bridge Proxy and the Coder server (for example, loopback or mTLS).

🔍 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

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
    Apply temporary workaround mitigate
    Ensure the Coder access URL uses a trusted certificate and secure the network path between the AI Bridge Proxy and the Coder server (for example, loopback or mTLS).

    パッチが適用されるまでの応急処置として、Ensure the Coder access URL uses a trusted certificate and secure the network path between the AI Bridge Proxy and the Coder server (for example, loopback or mTLS). を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade github.com/coder/coder/v2 to 2.32.7

    ステージング環境で 2.32.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

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

Affected packages

go github.com/coder/coder/v2
[{"type":"SEMVER","events":[{"introduced":"2.30.0"},{"fixed":"2.32.7"}]}]
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