Answer in brief
CVE-2026-55435 records a Medium severity (CVSS 5.4) vulnerability in Suspended Coder users retain access to AI Bridge LLM proxy endpoints. The current sources do not mark it as known exploited. The current feed maps coder/coder (generic), github.com/coder/coder/v2 (go), github.com/coder/coder/v2 (go), github.com/coder/coder/v2 (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps coder/coder (generic), github.com/coder/coder/v2 (go), github.com/coder/coder/v2 (go), github.com/coder/coder/v2 (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| coder/codergeneric | >= 2.34.0, < 2.34.2 || >= 2.33.0, < 2.33.8 || >= 2.30.0, < 2.32.7 | Not reported |
| github.com/coder/coder/v2go | >=2.34.0,<2.34.2 | 2.34.2 |
| github.com/coder/coder/v2go | >=2.33.0,<2.33.8 | 2.33.8 |
| github.com/coder/coder/v2go | >=2.30.0,<2.32.7 | 2.32.7 |
Published upstream
Jul 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 6, 2026
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, AI Bridge proxy endpoints authenticate via `Server.IsAuthorized` in `coderd/aibridgedserver`, which validates key format, expiry, secret and deleted or system users but does not check whether the account is suspended. Because suspension does not revoke existing API keys, a suspended user's unexpired token keeps working. Practical impact is limited to already-issued API keys of suspended users until those keys are deleted. Versions 2.32.7, 2.33.8, and 2.34.2 patch the issue. As a workaround, on suspension, delete the user's API keys via `DELETE /api/v2/users/{user}/keys`.
Quoted source text, attributed separately from HOL analysis.