# CVE-2026-55076: Coder's OIDC email_verified type coercion bypass enables account takeover via unverified email linking > Attackers can take over accounts by exploiting OIDC email verification bypass in Coder's development environment provisioning platform. - **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Jul 2026 - **Updated:** 8 Jul 2026 - **Also known as:** GHSA-75vm-6w67-gwvp, GO-2026-5907 ## What is CVE-2026-55076? CVE-2026-55076 is a high-severity authentication bypass vulnerability in coder, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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, Coder's OIDC callback checked `email_verified` with a direct Go `bool` type assertion. When an IdP returned the claim as a non-boolean (for example the string `"false"`) or omitted it, the assertion failed open and the email was treated as verified. Combined with an unconditional email-based account fallback, this enabled account takeover. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 coerces `email_verified` across bool, string and numeric types (fail-closed) and blocks the email fallback when the matched user already has a different linked IdP subject. As a workaround, ensure the IdP returns `email_verified` as a native JSON boolean. The email-fallback linking issue has no configuration workaround; upgrading is required. Weakness: CWE-704 (Incorrect Type Conversion or Cast), CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2026-55076? 10 open source packages ship an affected version, including github.com/coder/coder/v2 and github.com/coder/coder. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/coder/coder/v2` | Go | All versions | 2.29.17, 2.32.7, 2.33.8, 2.34.2 | | `github.com/coder/coder/v2` | Go | All versions | 2.29.17 | | `github.com/coder/coder/v2` | Go | All versions | 2.29.17 | | `github.com/coder/coder/v2` | Go | From 2.30.0 | 2.32.7 | | `github.com/coder/coder/v2` | Go | From 2.30.0 | 2.32.7 | | `github.com/coder/coder/v2` | Go | From 2.33.0 | 2.33.8 | | `github.com/coder/coder/v2` | Go | From 2.33.0 | 2.33.8 | | `github.com/coder/coder/v2` | Go | From 2.34.0 | 2.34.2 | | `github.com/coder/coder/v2` | Go | From 2.34.0 | 2.34.2 | | `github.com/coder/coder` | Go | All versions | None | Products: Coder Coder. ## How do I fix CVE-2026-55076? Upgrade github.com/coder/coder/v2 to a fixed version for your release line: 2.29.17, 2.32.7, 2.33.8 or 2.34.2. ## Is CVE-2026-55076 being exploited? There is no known exploitation of CVE-2026-55076 in the wild and no public exploit code. ## Other vulnerabilities in coder - [CVE-2026-46354](https://insights.sbomify.com/CVE-2026-46354/): Coder: PKCS#7 signature bypass in Azure instance identity allows unauthenticated agent token theft (critical 9.1) - [CVE-2026-55429](https://insights.sbomify.com/CVE-2026-55429/): Coder's workspace app upsert allows cross-workspace agent rebinding via user-controlled app ID (high 8.7) - [CVE-2026-55427](https://insights.sbomify.com/CVE-2026-55427/): Coder vulnerable to SSH config injection via unsanitized server-supplied values in `coder config-ssh` (high 8.3) - [CVE-2026-55428](https://insights.sbomify.com/CVE-2026-55428/): Coder: Route hijacking through lack of validation of agent-supplied AllowedIPs in tailnet coordinator (high 8.2) - [CVE-2024-27918](https://insights.sbomify.com/CVE-2024-27918/): Coder's OIDC authentication allows email with partially matching domain to register (high 8.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-55076 and fix it if it is affected. What it is: CVE-2026-55076 is a high-severity authentication bypass vulnerability in coder, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-55076 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/coder/coder/v2 (Go): affected all versions; fixed in 2.29.17, 2.32.7, 2.33.8, 2.34.2 - github.com/coder/coder/v2 (Go): affected all versions; fixed in 2.29.17 - github.com/coder/coder/v2 (Go): affected all versions; fixed in 2.29.17 - github.com/coder/coder/v2 (Go): affected from 2.30.0; fixed in 2.32.7 - github.com/coder/coder/v2 (Go): affected from 2.30.0; fixed in 2.32.7 - github.com/coder/coder/v2 (Go): affected from 2.33.0; fixed in 2.33.8 - github.com/coder/coder/v2 (Go): affected from 2.33.0; fixed in 2.33.8 - github.com/coder/coder/v2 (Go): affected from 2.34.0; fixed in 2.34.2 - github.com/coder/coder/v2 (Go): affected from 2.34.0; fixed in 2.34.2 - github.com/coder/coder (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-55076/ (Markdown: https://insights.sbomify.com/CVE-2026-55076/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55076 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55076 - OSV: https://osv.dev/vulnerability/CVE-2026-55076 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-55076/ Summaries are generated and may contain mistakes; the official description above is the record.