Answer in brief
CVE-2026-55075 records a High severity (CVSS 7.4) vulnerability in Coder vulnerable to OIDC account takeover via email-based user matching and email_verified bypass. 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) and additional mapped packages. 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 7.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) and additional mapped packages. 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 || < 2.29.17 | 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 |
| github.com/coder/coder/v2go | <2.29.17 | 2.29.17 |
Published upstream
Jul 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 8, 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. Prior to versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2, two flaws in Coder's OIDC login chained into account takeover. Email-based user matching fell back to linking by email without checking for an existing link to a different IdP subject and the `email_verified` claim was only enforced when present as a boolean `false` so an absent or non-boolean claim was treated as verified. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 restricts the email fallback to first-time and legacy linking and defaults `email_verified` to false when the claim is absent or of an unexpected type. As a workaround, configure the OIDC provider to disallow self-registration or to require email verification before issuing tokens.
Quoted source text, attributed separately from HOL analysis.