Coder up to 2.29.6/2.32.6/2.33.7/2.34.1 OIDC Callback assertion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Coder up to 2.29.6/2.32.6/2.33.7/2.34.1. The impacted element is an unknown function of the component OIDC Callback Handler. Such manipulation leads to assertion. This vulnerability is traded as CVE-2026-55076. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability, which was classified as critical, has been found in Coder up to 2.29.6/2.32.6/2.33.7/2.34.1. Affected by this issue is an unknown code block of the component OIDC Callback Handler. The manipulation with an unknown input leads to a assertion vulnerability. Using CWE to declare the problem leads to CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-55076 since 06/16/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 2.29.7, 2.32.7, 2.33.8 or 2.34.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-42129). Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
- 2.29.0
- 2.29.1
- 2.29.2
- 2.29.3
- 2.29.4
- 2.29.5
- 2.29.6
- 2.32.0
- 2.32.1
- 2.32.2
- 2.32.3
- 2.32.4
- 2.32.5
- 2.32.6
- 2.33.0
- 2.33.1
- 2.33.2
- 2.33.3
- 2.33.4
- 2.33.5
- 2.33.6
- 2.33.7
- 2.34.0
- 2.34.1
Website
- Product: https://github.com/coder/coder/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AssertionCWE: CWE-617
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: Coder 2.29.7/2.32.7/2.33.8/2.34.2
Timeline
06/16/2026 CVE reserved07/07/2026 VulDB entry created
07/08/2026 Advisory disclosed
07/08/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-55076 (🔒)
GCVE (CVE): GCVE-0-2026-55076
GCVE (VulDB): GCVE-100-376724
EUVD: 🔒
Entry
Created: 07/08/2026 00:42Updated: 07/08/2026 03:56
Changes: 07/08/2026 00:42 (52), 07/08/2026 03:56 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.