Skip to main content
VulnerabilityPublished

CVE-2026-55075: V2 · Coder vulnerable to OIDC account takeover via email-based user matching and email_verified bypass

Affects github.com/coder/coder/v2Source GCVE Database

0
Compare

Not known to be exploited · CVSS 7.4 High : upgrade to 2.34.2 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.34.2, 2.33.8, 2.32.7 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
Gogithub.com/coder/coder/v2Affected
  • >=2.34.0 <2.34.2
Fixed in
  • 2.34.2
Gogithub.com/coder/coder/v2Affected
  • >=2.33.0 <2.33.8
Fixed in
  • 2.33.8
Gogithub.com/coder/coder/v2Affected
  • >=2.30.0 <2.32.7
Fixed in
  • 2.32.7
Gogithub.com/coder/coder/v2Affected
  • <2.29.17
Fixed in
  • 2.29.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Official patches are available and have been backported to all supported release lines: 2.29.17, 2.32.7, 2.33.8, and 2.34.2. Users should upgrade to these versions or later to remediate the vulnerability. As a workaround, configuring the OIDC provider to disallow self-registration or require email verification before issuing tokens can reduce risk. No other mitigations are indicated by the vendor advisory.

Description

### Summary 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. ### Impact 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. ### Patches 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: | Release line | Patched version | |---|---| | 2.34 | [v2.34.2](https://github.com/coder/coder/releases/tag/v2.34.2) | | 2.33 | [v2.33.8](https://github.com/coder/coder/releases/tag/v2.33.8) | | 2.32 | [v2.32.7](https://github.com/coder/coder/releases/tag/v2.32.7) | | 2.29 (ESR) | [v2.29.17](https://github.com/coder/coder/releases/tag/v2.29.17) | ### Workarounds Configure the OIDC provider to disallow self-registration or to require email verification before issuing tokens. ### Resources - Fix: #25712, #25713 ### Credits Coder would like to thank Anthropic's Security Team (ANT-2026-22450) for independently disclosing this issue!

References

Community reviews

Loading reviews…