CVE-2026-55076

Coder's OIDC email_verified type coercion bypass enables account takeover via unverified email linking

HIGH
7.4
CVSS Score
Published: July 7, 2026 at 10:23 PM UTC
Updated: July 8, 2026 at 08:05 PM UTC
1 product affected across 1 vendorCoder

Using coder by coder?

Get instant alerts when new vulnerabilities affect coder - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.4
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.29.17v < 2.32.7v < 2.33.8v < 2.34.22.30.0 ≤ v < 2.32.72.33.0 ≤ v < 2.33.82.34.0 ≤ v < 2.34.2
Affected range stops below 2.29.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.32.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.33.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.34.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (7)

x_refsource_CONFIRMPatchVendor Advisory
Source: cverecord
https://github.com/coder/coder/security/advisories/GHSA-75vm-6w67-gwvp
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/coder/coder/pull/25712
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/coder/coder/pull/25713
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/coder/coder/releases/tag/v2.29.17
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/coder/coder/releases/tag/v2.32.7
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/coder/coder/releases/tag/v2.33.8
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/coder/coder/releases/tag/v2.34.2

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.4HIGHGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-287CWE-704

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card