CVE-2026-55075

Coder vulnerable to OIDC account takeover via email-based user matching and email_verified bypass

An attacker who could authenticate at the configured OIDC provider with an email matching a victim's Coder account could log in as that victim and gain full access to their workspaces, templates and resources. This required OIDC authentication, attacker control of a matching email at the IdP and a victim account not yet linked to a different IdP subject.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-55075 has a CVSS score of 7.4 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.34.2, 2.33.8, 2.32.7, 2.29.17); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The fix 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.

The fix was backported to all supported release lines:

1. What is CVE-2026-55075? CVE-2026-55075 is a high-severity improper authentication vulnerability in github.com/coder/coder/v2 (go), affecting versions >= 2.34.0, < 2.34.2. It is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2026-55075? CVE-2026-55075 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/coder/coder/v2 are affected by CVE-2026-55075? github.com/coder/coder/v2 (go) versions >= 2.34.0, < 2.34.2 is affected.
4. Is there a fix for CVE-2026-55075? Yes. CVE-2026-55075 is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17. Upgrade to this version or later.
5. Is CVE-2026-55075 exploitable, and should I be worried? Whether CVE-2026-55075 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-55075 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-55075?
   • Upgrade github.com/coder/coder/v2 to 2.34.2 or later
   • Upgrade github.com/coder/coder/v2 to 2.33.8 or later
   • Upgrade github.com/coder/coder/v2 to 2.32.7 or later
   • Upgrade github.com/coder/coder/v2 to 2.29.17 or later

Other vulnerabilities in github.com/coder/coder/v2