CVE-2026-55076: Coder account takeover via OIDC email verification bypass

CVE-2026-55076 · Severity: high · CVSS 7.4 · Published 2026-07-07

Coder, a platform for managing remote development environments, contained a flaw in how it verified user identities during login. An attacker could potentially take over a victim's account by exploiting a weakness in how the system confirms email addresses from third-party identity providers. This could lead to unauthorized access to sensitive development environments and corporate data.

Technologies: Coder, github.com/coder/coder (Go), github.com/coder/coder/v2 (Go). Vendors: Coder, Go.

Quick answers

Is CVE-2026-55076 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-55076 being exploited in the wild.
How severe is CVE-2026-55076?
High severity, with a CVSS score of 7.4, published 7 July 2026.
Which products and versions are affected?
Coder < 2.29.17, >= 2.30.0 < 2.32.7, >= 2.33.0 < 2.33.8, >= 2.34.0 < 2.34.2; github.com/coder/coder (Go) SEMVER:introduced=0; github.com/coder/coder/v2 (Go) SEMVER:introduced=0,fixed=2.29.17,introduced=2.30.0,fixed=2.32.7,introduced=2.33.0,fixed=2.33.8,introduced=2.34.0,fixed=2.34.2, SEMVER:introduced=2.34.0,fixed=2.34.2.
Is there a fix for CVE-2026-55076?
Yes. github.com/coder/coder/v2 (Go): upgrade to 2.34.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55076 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-55076?
Check whether you run Coder, github.com/coder/coder (Go) or github.com/coder/coder/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/coder/coder/v2 (Go): upgrade to 2.34.2 or later
    go get github.com/coder/coder/v2@v2.34.2

Technical details

A vulnerability exists in Coder's OIDC implementation due to improper type assertion and insecure account linking logic. The OIDC callback used a Go type assertion for the 'email_verified' claim that failed open if the Identity Provider (IdP) returned a non-boolean value (like a string) or omitted the claim entirely. When combined with an unconditional email-based account fallback that matched users by email rather than a unique IdP subject, an attacker could register a victim's email at a malicious or misconfigured IdP to gain access to the victim's Coder account. The fix implements strict type coercion for the verification claim and restricts email-based fallback to first-time account linking only.

Affected products

  • Coder Coder < 2.29.17, >= 2.30.0 < 2.32.7, >= 2.33.0 < 2.33.8, >= 2.34.0 < 2.34.2

Identifiers

  • CVE-2026-55076
  • GHSA-75vm-6w67-gwvp
  • GO-2026-5907

Timeline

  • 2026-05-27: other: Fixes submitted via pull requests
  • 2026-06-12: patched: Security release v2.29.17 published
  • 2026-07-07: disclosed: CVE published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.